APRS Packet Errors for EA7UH (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
20181212053746EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212055306EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212060825EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212062349EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212063909EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212065440EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212070959EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212072521EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212074046EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212075615EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212081139EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212082713EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212084236EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212085757EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212091322EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212092848EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212094411EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212095935EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212101457EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212103031EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212104557EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212111644EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz