APRS Packet Errors for G0VNP (last 24 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
20260312184926G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260312192153G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260312195420G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260312202649G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260312205913G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260312213135G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260312220357G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260313180038G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz
20260313183309G0VNP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G0VNP-DP!5051.41N/001-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 438.0250 MHz