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
20190217160854EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217162540EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217164217EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217165856EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217171556EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217173242EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217174940EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217180620EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217182253EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217183954EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217185655EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217191339EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217193014EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217194654EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217200345EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217202018EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217203651EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217205322EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217211002EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz
20190217212641EA1HNC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HNC-DP!4220.55N/-03-41.98rRNG0034 IPSC2-EA4Master MMDVM 434.3000 MHz