APRS Packet Errors for G4TGV (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
20260311151846G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311155113G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311162344G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311165614G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311172843G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311180111G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311183337G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311190605G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311193831G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz
20260311201057G4TGV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G4TGV-DP!5212.93N/000-27.48rRNG0034 IPSC2-DVSPh-F MMDVM 434.5000 MHz