APRS Packet Errors for VK6HKE (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
20241121160548VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121164336VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121172045VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121175740VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121183501VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121191156VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121194929VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121202723VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz
20241121210505VK6HKE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6HKE-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.1000@-7.0 MHz