APRS Packet Errors for VK4RM (last 24 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
20250401154705VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401162439VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401170223VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401174006VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401181806VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401185544VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401193332VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401201149VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401204957VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401212831VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401220705VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401224513VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250401232354VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402000156VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402004008VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402011804VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402015601VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402023357VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402031158VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402035008VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402042943VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402050804VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz
20250402054608VK4RM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4RM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.2000 MHz