APRS Packet Errors for HK4Y-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
20260209092107HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@092107h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209095108HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@095107h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209102109HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@102108h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209105110HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@105109h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209112110HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@112110h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209115111HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@115111h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209122112HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@122112h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209125113HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@125113h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209132114HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@132114h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209135115HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@135115h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209142116HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@142115h0613.85N/07536.74W-APRS_MEDELLIN_HKNET
20260209145117HK4Y-1>APWW11,TCPIP*,qAC,T2CHILE:@145117h0613.85N/07536.74W-APRS_MEDELLIN_HKNET