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
20190322040547EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322042224EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322043858EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322045531EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322051206EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322052843EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322054525EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322060211EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322061852EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322063537EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322065219EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322070908EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322072550EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322074239EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322075932EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322081626EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322083322EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322085021EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322090706EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322092402EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20190322094045EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz