APRS Packet Errors for HK3OCH-10 (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
20260208133817HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208140818HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208143818HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208150819HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208153820HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208160821HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208163821HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208170821HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208173821HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208180821HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208183821HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota
20260208190822HK3OCH-10>BEACON,TCPIP*,qAC,SECOND:!0437.28N/07407.94W&HK APRS Group Bogota