APRS Packet Errors for E25DQY-2 (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
20260208153653E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208153940E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208154126E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208162010E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208171610E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208172433E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208172549E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208174050E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208174601E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208175110E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE
20260208175552E25DQY-2>APE32L,TCPIP*,qAC,APRSTH:!1309.31N/10055.75E&IGate MODE