APRS Packet Errors for EA4DGY (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
20190418091458EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418093250EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418095015EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418100733EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418102449EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418104201EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418105926EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418111637EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418113355EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418115113EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418120822EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418122552EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418124317EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418130029EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418131758EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418133506EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418135222EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418140943EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418142650EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418144352EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190418150054EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz