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
20190217163237EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217164908EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217170541EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217172218EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217173859EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217175529EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217181208EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217182848EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217184521EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217190204EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217191837EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217193514EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217195159EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217200844EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217202526EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217204208EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217205846EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217211521EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217213152EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217214830EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217220501EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz
20190217222136EA7JOE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JOE-DP!3736.60N/-03-10.80rRNG0034 IPSC2-EA-Hotspot MMDVM 438.0750 MHz