APRS Packet Errors for VK3NES (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
20260524145500	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260524153206	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260524164554	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260524172227	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260524175900	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260524191250	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260524194945	VK3NES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3NES-DP!37-0.00S/14503.60ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz