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
20181212231006EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212232520EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212234037EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212235545EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213001052EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213002601EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213004111EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213005618EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213011126EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213012647EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213014157EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213015705EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213021213EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213022720EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213024230EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213025738EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213031245EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213032753EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213034303EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213035810EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213041318EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213042825EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213044335EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181213045842EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz