APRS Packet Errors for G4ZWH (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
20250918141411	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918144606	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918151759	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918154954	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918162145	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918165338	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918172530	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918175719	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz
20250918182906	G4ZWH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4ZWH-DP!5213.20N/000-16.80rRNG0034 IPSC2-DVSPh-F MMDVM 430.2000 MHz