APRS Packet Errors for G4KWT (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
20250918120630G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918141411G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918144606G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918151759G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918154954G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918162145G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918165338G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz
20250918172530G4KWT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4KWT-DP!5127.53N/000-52.89rRNG0034 IPSC2-DVSPh-F MMDVM 430.0250 MHz