APRS Packet Errors for HS3XMW-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
20260209103655HS3XMW-1>AESPG4,TCPIP*,qAC,T2HK:=1445.40N/10341.86E#Indy Igate
20260209105102HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209112425HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209115731HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209123054HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209130400HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209133706HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209141013HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209144320HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209151627HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209154933HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate
20260209162239HS3XMW-1>AESPG4,TCPIP*,qAC,T2OSAKA:=1445.40N/10341.86E#Indy Igate