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
20181209163808EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209165344EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209170907EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209172433EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209174007EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209175544EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209181111EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209182646EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209184227EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209185753EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209191317EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209192841EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209194408EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209195931EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209201457EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209203020EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209204548EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209210116EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209211641EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209213203EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209214751EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209220329EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181209221853EA2COE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2COE-DP!4139.56N/000-52.44rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz