APRS Packet Errors for VK1MDJ (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
20250509092216	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509100033	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509103837	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509111635	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509115434	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509123234	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509131020	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509142528	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20250509150259	VK1MDJ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK1MDJ-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz