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
20190219083413EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219085041EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219090713EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219092341EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219094012EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219095642EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219101313EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219102943EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219104610EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219110244EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219111925EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219113614EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219115242EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219120912EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219122543EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219124214EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219125843EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219131512EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219133150EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219134817EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219140448EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190219142120EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz