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
20181215175734EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 432.1000 MHz
20181215181302EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 432.1000 MHz
20181215182826EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181215184352EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181215185919EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181215191451EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181215194548EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181215200115EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.84N/-04-26.81WrRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz
20181215201734EA7JTR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JTR-DP!3641.81N/-04-26.80rRNG0034 IPSC2-EA-Hotspot MMDVM 434.3000 MHz