APRS Packet Errors for G6VEY (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
20260201114232G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201121313G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201124355G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201131435G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201134517G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201141602G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201144642G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201151726G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz
20260201154823G6VEY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6VEY-DP!5245.44N/000-22.38rRNG0034 IPSC2-FreeSTAR MMDVM 438.8000 MHz