APRS Packet Errors for VK2ODN (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
20251114193806VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114201432VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114205043VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114212655VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114220315VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114223852VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114231429VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251114235020VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251115002615VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz
20251115010210VK2ODN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2ODN-DP!15036.72S/03442.66rRNG0034 IPSC2-VKHOTSPOT MMDVM 440.8000 MHz