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
20190220071907EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220073549EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220075227EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220080858EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220082542EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220084232EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220091601EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220093245EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220094930EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220100607EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220102249EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220103941EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220105637EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220111327EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220113028EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220114721EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220120405EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220122045EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220123727EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220125435EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190220131114EA4BA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4BA-DP!4016.84N/-03-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz