APRS Packet Errors for VK6STX (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
20260112072057VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112075649VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112083238VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112090832VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112094440VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112102104VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112105701VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112113259VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112120906VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz
20260112124451VK6STX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK6STX-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 433.7000 MHz