APRS Packet Errors for G6CON (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
20260604125525G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604132712G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604135857G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604143043G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604150228G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604153416G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604160606G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604163753G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz
20260604170940G6CON>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6CON-DP!51245300.00N/13103rRNG0034 IPSC2-DVSPh-F MMDVM 438.3000 MHz