APRS Packet Errors for EA7HMY (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
20181213070559EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213072119EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213073640EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213075209EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213080734EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213082256EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213083816EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213085340EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213090907EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213092432EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213094011EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213095548EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213101129EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213102715EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213104253EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213105826EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213111400EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz
20181213112937EA7HMY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HMY-DP!3852.97N/-04-45.80rRNG0034 IPSC2-EA-Hotspot MMDVM 439.8750 MHz