APRS Packet Errors for EA7JDR (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
20190216074229	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216075854	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216081531	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216083200	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216084831	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216090458	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216092127	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216093806	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216095437	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216101112	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216102746	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216104415	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216110100	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216111741	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216113411	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216115047	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216120722	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216122359	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216124041	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216125712	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216131349	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz
20190216133024	EA7JDR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JDR-DP!3742.06N/-05-16.69rRNG0034 IPSC2-EA-Hotspot MMDVM 439.9750 MHz