APRS Packet Errors for EA7JOE (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
20190422142751EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422144438EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422150118EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422151804EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422153452EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422155136EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422160826EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422162511EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422164156EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422165838EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422171521EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422173204EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422174849EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422180534EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422182216EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422183902EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422185545EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422191248EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422192931EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422194614EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422200258EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190422201938EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz