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
20181211221918EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181211223428EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181211224937EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181211230446EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181211231957EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181211233505EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181211235015EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212000523EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212002034EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212003542EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212005051EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212010600EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212012112EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212013621EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212015128EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212020637EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212022147EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212023655EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212025202EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212030711EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212032221EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212033729EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212035236EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz
20181212040744EA7HNY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNY-DP!4019.70N/-03-51.33rRNG0034 IPSC2-EA1Master MMDVM 436.0000 MHz