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
20181117100732EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117102255EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117103811EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117105328EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117110855EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117112424EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117113941EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117115459EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117121018EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117122537EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117124057EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117125614EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117131141EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117132700EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117134220EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117135746EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117141305EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117142823EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117144342EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117145859EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117151417EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117152942EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117154507EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz
20181117160025EA7HNF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7HNF-DP!4019.50N/-03-52.11rRNG0034 IPSC2-EA4Master MMDVM 438.1500 MHz