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
20190116090710EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116092316EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116093914EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116095512EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116101114EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116102800EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116104448EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116110128EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116111811EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116113427EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116115057EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116120747EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116122437EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116124143EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116125834EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116131445EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116133106EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116134730EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116140338EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116141946EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116143558EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190116145214EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz