APRS Packet Errors for K3CAL-1 (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
20260209145100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209152100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209155100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209162100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209165100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209172100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209175100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209182100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209185100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209192100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209195100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz
20260209202100WG3K-4>APBPQ1,TCPIP*,qAC,WG3K-NJ:;K3CAL-1 *111111z3832.07N/07635.31W#145.070MHz