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
20181212231007EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212232528EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212234050EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181212235612EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213001132EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213002654EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213004214EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213005738EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213011300EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213012820EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213014338EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213015901EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213021421EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213022944EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213024512EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213030037EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213031556EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213033115EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213034633EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213040158EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213041718EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213043237EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213044757EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz
20181213050320EA7UH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7UH-DP!3717.40N/-06-22.62rRNG0034 IPSC2-EA-Hotspot MMDVM 438.1500 MHz