APRS Packet Errors for PY5BK-12 (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
20260209185059PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209190100PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209191101PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209192102PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209193103PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209194105PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209195106PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209200106PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209201108PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209202109PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209203110PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G
20260209204111PY5BK-12>APBK99,TCPIP,qAS,PY5BK:!2303.15S/05101.79W>Tracker 4G