APRS Packet Errors for VK3GSM (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
20250514180227VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514183932VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514191633VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514195453VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514203229VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514211121VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514214928VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514222731VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514230625VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250514234341VK3GSM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3GSM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz