APRS Packet Errors for G6AHY-DP (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
20260208181539G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208184747G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208191951G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208195155G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208202357G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208205559G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208212759G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208215957G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208223151G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz
20260208230354G6AHY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6AHY-DP!5117.76N/00139.42WrRNG0034 IPSC2-DVSPh-F MMDVM 438.8000 MHz