APRS Packet Errors for VK3AIJ (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
20260417005118VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417012924VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417020719VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417024606VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417032350VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417040138VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417044017VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417051846VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417055645VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz
20260417063421VK3AIJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3AIJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.6000 MHz