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
20190322044907EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322050544EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322052218EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322053854EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322055529EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322061205EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322062838EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322064513EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322070149EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322071823EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322073501EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322075138EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322080811EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322082447EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322084126EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322085800EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322091437EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322093111EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322094748EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322100432EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322102113EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20190322103747EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.46N/-06-22.65rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz