APRS Packet Errors for VK2ASU (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
20250331121054VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331124859VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331132709VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331140500VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331144258VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331152104VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331155859VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331163646VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331171443VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250331175230VK2ASU>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ASU-DP!15135.00N/03245.00rRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz