APRS Packet Errors for VK3CDE (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
20250126000524	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126004409	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126012232	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126020103	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126023934	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126031836	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126035735	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126043557	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20250126051449	VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz