APRS Packet Errors for G0VNP (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
20261020205514G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261020212706G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261020215844G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261020223032G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261020230220G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261020233354G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261021000527G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261021003658G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261021014001G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz
20261021021134G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 431.1000 MHz