APRS Packet Errors for EA7JTR (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
20190219071148EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219072813EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219074443EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219080113EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219081745EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219083413EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219085041EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219090713EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219092341EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219094012EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219095642EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219101313EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219102943EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219104610EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219110244EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219111925EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219113614EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219115242EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219120912EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219122543EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219124214EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz
20190219125843EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 433.3750 MHz