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
20241224121909VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224125654VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224133435VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224141207VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224144942VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224152713VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224160446VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224164253VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224172049VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20241224175821VK3CDE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3CDE-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz