APRS Packet Errors for EA9UV (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
20181211212536EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211214057EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211215620EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211221150EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211222710EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211224231EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211225751EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211231316EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211232837EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181211234358EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz