APRS Packet Errors for VK3NAR (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
20260209145853VK3NAR>APN000,TCPXX*,qAX,CWOP-3:@091458z3805.55S/14511.18E_000/000g000t064r000p000P000b10127h84L000eMB63
20260209152854VK3NAR>APN000,TCPXX*,qAX,CWOP-5:@091528z3805.55S/14511.18E_000/000g000t064r000p000P000b10125h84L000eMB63
20260209155853VK3NAR>APN000,TCPXX*,qAX,CWOP-6:@091558z3805.55S/14511.18E_000/000g000t063r000p000P000b10124h83L000eMB63
20260209162854VK3NAR>APN000,TCPXX*,qAX,CWOP-5:@091628z3805.55S/14511.18E_000/000g000t064r000p000P000b10123h83L000eMB63
20260209165857VK3NAR>APN000,TCPXX*,qAX,CWOP-7:@091658z3805.55S/14511.18E_000/000g000t064r000p000P000b10124h84L000eMB63
20260209172859VK3NAR>APN000,TCPXX*,qAX,CWOP-3:@091728z3805.55S/14511.18E_000/000g000t064r000p000P000b10123h83L000eMB63
20260209175858VK3NAR>APN000,TCPXX*,qAX,CWOP-4:@091758z3805.55S/14511.18E_000/000g000t064r000p000P000b10123h82L000eMB63
20260209185902VK3NAR>APN000,TCPXX*,qAX,CWOP-5:@091859z3805.55S/14511.18E_000/000g000t064r000p000P000b10127h84L000eMB63
20260209192901VK3NAR>APN000,TCPXX*,qAX,CWOP-4:@091929z3805.55S/14511.18E_000/000g000t063r000p000P000b10129h83L000eMB63
20260209195901VK3NAR>APN000,TCPXX*,qAX,CWOP-4:@091959z3805.55S/14511.18E_000/000g000t063r000p000P000b10131h82L005eMB63