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
20190319234828EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320000516EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320002158EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320003842EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320005528EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320011205EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320012843EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320014523EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320020203EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320021841EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320023521EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320025210EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320030852EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320032529EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320034213EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320035852EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320041533EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320043213EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320044853EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320050530EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320052209EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320053849EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz