APRS Packet Errors for HS6YHE-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
20260208170247HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208172917HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208175713HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208182428HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208185259HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208191942HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208194502HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208201126HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208203656HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208210420HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208213156HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208215956HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK
20260208222529HS6YHE-1>APRSAI,TCPIP*,qAC,APRSTH:!1649.37NI10121.56E&IGATE WRT54GL LOMSAK