APRS Packet Errors for EA4BA (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20190626131233EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626132922EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626134612EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626140308EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626142004EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626143707EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626145403EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626151058EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626152751EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626154451EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626160143EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626161834EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626163536EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626165230EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626170928EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626172658EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626174357EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626180057EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626181758EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626183504EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190626185212EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz