APRS Packet Errors for G6ZQT-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
20260208131733G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208142150G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208150245G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208153455G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208160705G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208163914G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208171121G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208174330G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208181539G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz
20260208184747G6ZQT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6ZQT-DP!5203.76N/00108.53ErRNG0034 IPSC2-DVSPh-F MMDVM 434.0000 MHz