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
20190424183110EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424184754EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424190449EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424192139EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424193830EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424195516EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424201212EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424202903EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424204557EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424210239EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424211925EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424213612EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424215302EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424220948EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424222633EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424224317EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424230000EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424231644EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424233331EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190424235017EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190425000700EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.52N/-06-22.56rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz