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
20181212045814EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212051328EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212052842EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212054404EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212055918EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212061436EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212062951EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212064511EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212070028EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212071544EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212073059EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212074620EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212080136EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212081658EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212083232EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212084759EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212090327EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212091855EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212093422EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212094954EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212100523EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212102111EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20181212103654EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz