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
20190215202607EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215204259EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215205931EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215211603EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215213233EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215214901EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215220534EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215222224EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215223904EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215225538EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215231208EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215232842EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190215234510EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216000140EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216001807EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216003447EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216005116EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216010742EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216012408EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216014039EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216015704EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190216021327EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz