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
20190217000250EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217001915EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217003539EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217005208EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217010830EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217012454EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217014117EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217015744EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217021410EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217023053EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217024726EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217030353EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217032017EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217033640EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217035303EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217040934EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217042557EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217044221EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217045843EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217051512EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217053137EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190217054805EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz