APRS Packet Errors for EA1HNC (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
20190218010223EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218011849EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218013518EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218015144EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218020813EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218022439EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218024114EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218025746EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218031417EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218033043EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218034711EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218040342EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218042008EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218043635EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218045304EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218050930EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218052555EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218054223EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218055852EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218061518EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218063152EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190218064822EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz