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
20190222153614EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222155246EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222160923EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222162558EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222164249EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222165932EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222171614EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222173254EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222174935EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222180615EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222182256EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222183933EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222185620EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222191259EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222192940EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222194621EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222200309EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222201955EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222203641EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222205315EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222210949EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20190222212626EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz