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
20181019143410EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019144940EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019150503EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019152033EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019153559EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019155122EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019160645EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019162208EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019163742EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019165305EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019170828EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019172350EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019173923EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019175501EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019181031EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019182555EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019184130EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019185654EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019191224EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019192754EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019194345EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019195915EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz
20181019201436EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA-Hotspot MMDVM 436.0000 MHz