APRS Packet Errors for EA1HG (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
20190917013643EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917015154EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917020705EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917022216EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917023730EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917025241EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917030750EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917032301EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917033814EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917035325EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917040835EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917042346EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917043859EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917045409EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917050919EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917052430EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917053943EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917055454EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917061005EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917062515EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917064029EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917065540EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz
20190917071051EA1HG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HG-DP!4144.00N/-50-23.99rRNG0034 IPSC2-EA4Master MMDVM 434.4000 MHz