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
20190320075243EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320080929EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320082624EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320084327EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320090018EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320091715EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320093402EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320095102EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320100747EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320102456EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320104146EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320105841EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320111533EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320113231EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320114919EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320120611EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320122310EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320123958EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320125642EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320131327EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190320133012EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz