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
20181016145710EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016151235EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016152804EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016154338EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016155904EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016161428EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016162954EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016164909EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016170445EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016172014EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016174700EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016180230EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016181753EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016183316EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016184841EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016190404EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016191929EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016193452EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016195017EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016200546EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016202116EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181016203638EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz