APRS Packet Errors for VK2WGW (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
20251215195849VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251215203506VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251215211130VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251215214738VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251215222421VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251215230052VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251215233659VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251216001327VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251216004938VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20251216012552VK2WGW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2WGW-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz