APRS Packet Errors for VK4KDB (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
20240429051700VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429055417VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429063155VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429070932VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429074717VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429082435VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429090224VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429093951VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429101751VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz
20240429105519VK4KDB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4KDB-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.5750 MHz