APRS Packet Errors for G6IGA (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
20250226193419G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226200614G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226203806G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226210958G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226214150G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226224531G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226231718G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250226234903G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20250227002046G6IGA>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6IGA-DP!5125.84N/000-54.66rRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz