APRS Packet Errors for VK3KYY (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
20250314174638	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314182417	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314190207	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314194013	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314201911	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314205747	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314213554	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz
20250314221415	VK3KYY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3KYY-DP!14500.00N/038-0.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000@+7.0 MHz