APRS Packet Errors for EA7HNY (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
20181018191835EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018193357EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018194925EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018200455EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018202017EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018203538EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018205100EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018210624EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018212146EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018213708EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018215228EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018220751EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018222400EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018223920EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018225439EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018231007EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018232526EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018234046EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181018235606EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019001129EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019002649EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019004209EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019005728EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz