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
20190218171537EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218173143EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218174750EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218180403EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218182024EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218183646EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218185315EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218190938EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218192612EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218194233EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218195856EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218201514EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218203137EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218204756EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218210414EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218212033EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218213656EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218215317EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218220938EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218222601EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218224225EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20190218225845EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz