APRS Packet Errors for G6FGY (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
20251216151736G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216153257G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216154742G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216160441G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216161748G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216170813G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216171801G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216173959G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216174807G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216181145G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216181813G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216184332G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216184821G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216191530G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216191829G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216194712G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216194835G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216201841G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216201908G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz
20251216204847G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-M MMDVM 438.1000 MHz
20251216205103G6FGY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6FGY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-DVSPh-F MMDVM 439.2000 MHz