APRS Packet Errors for VK2PGK (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
20250326125339	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326133137	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326140939	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326144902	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326152714	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326160508	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326164304	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326172101	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250326175906	VK2PGK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2PGK-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz