APRS Packet Errors for VK2JDC (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
20250911222119VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250911225821VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250911233513VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912001202VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912004850VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912012551VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912020256VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912024032VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912031747VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz
20250912035503VK2JDC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JDC-DP!34-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 145.3500 MHz