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
20181019173923EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019175501EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019181031EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019182555EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019184130EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019185654EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019191224EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019192754EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019194345EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019195915EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019201436EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019202958EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019204523EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019210045EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019211604EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019213125EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019214648EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181019220208EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz