APRS Packet Errors for VK2TST (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
20240508185328VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508193031VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508200740VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508204423VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508212117VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508215812VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508223521VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508231309VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240508235028VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20240509002755VK2TST>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TST-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz