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
20190220131114EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220132757EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220134433EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220140114EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220141749EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220143425EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220145109EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220150804EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220152446EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220154135EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220155820EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220161503EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220163138EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220164815EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220170451EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220172127EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220173804EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220175445EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220181139EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220182832EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220184517EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220190208EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz