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
20190615230233EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190615231916EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190615233559EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190615235245EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616000930EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616002614EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616004258EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616005944EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616011628EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616013326EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616015022EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616020716EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616022359EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616024043EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616025727EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616031413EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616033055EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616034740EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616040422EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616042109EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz
20190616043750EA4DGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4DGY-DP!4018.93N/-03-51.22rRNG0034 IPSC2-EA4Master MMDVM 438.2000 MHz