APRS Packet Errors for EA2COE (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
20191015171253EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015172811EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015174327EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015175848EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015181411EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015182932EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015184455EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015190016EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015191532EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015193049EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015194605EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015200125EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015201641EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015203155EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015204710EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015210226EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015211740EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015213255EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015214808EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015220324EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015221837EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20191015223354EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz