APRS Packet Errors for VK3EVT (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
20260425173919VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425181624VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425185321VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425193025VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425200723VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425204426VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425212132VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425215850VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425223735VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20260425231541VK3EVT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3EVT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz