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
20260208135150E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208141807E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208144237E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208150837E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208153331E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208160148E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208162912E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208165541E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208172259E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208174940E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208181729E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz
20260208184638E22HEO>APRSAI,TCPIP*,qAC,APRSFI-I3:!1349.12NI09946.47E&IGATE RATCHABURI 145.350MHz