APRS Packet Errors for EA7OR (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
20190923145854EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923151419EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923152942EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923154506EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923160035EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923161558EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923163121EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923164645EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923170213EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923171737EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923173302EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923174826EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923180352EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923181916EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923183438EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923185003EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923190529EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923192052EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923193617EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923195141EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923200707EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923202228EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz
20190923203750EA7OR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7OR-DP!3750.52N/-04-51.69rRNG0034 IPSC2-EA-Hotspot MMDVM 434.6000 MHz