APRS Packet Errors for E22HEO (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
20260209091421E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209094111E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209100755E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209103413E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209110244E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209112907E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209115410E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209121927E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209124631E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209131444E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209134128E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209140823E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260209143503E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz