APRS Packet Errors for VK2JXB (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
20250918142821VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918145913VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918153021VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918160054VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918163142VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918170245VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918173352VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918180458VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz
20250918183548VK2JXB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2JXB-DP!35-0.00S/15000.00ErRNG0034 IPSC2-GR-DMO2 MMDVM 435.0000 MHz