APRS Packet Errors for EA1HVS (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
20201204141829EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204144852EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204151916EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204154941EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204162019EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204165044EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204172115EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204175149EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204182222EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz
20201204185330EA1HVS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1HVS-DP!5000.00N/003-0.00WrRNG0034 IPSC2-EA1Master MMDVM 436.2000 MHz