APRS Packet Errors for EA7HNF (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
20190625140336EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625142025EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625143723EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625145428EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625151126EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625152824EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625154536EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625160230EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625161923EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625163701EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625165424EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625171135EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625172844EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625174544EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625180310EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625182013EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625183717EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625185422EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625191140EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625192841EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625194539EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190625200236EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz