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
20181215145253EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215150817EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215152339EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215153901EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215155422EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215160953EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215162519EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215164040EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215165607EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215171132EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215172652EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215174211EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215175734EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215181302EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215182826EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215184352EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215185919EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215191451EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215193013EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215194548EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215200115EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215201734EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz
20181215203302EA9UV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA9UV-DP!3553.20N/-05-19.46rRNG0034 IPSC2-EA-Hotspot MMDVM 435.1000 MHz