APRS Packet Errors for G1AAK-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
20260209110200G1AAK-1>APSN01,TCPIP*,qAC,T2TEXAS:=5322.35N/00243.42W-231/000/A=000087Beacon on hourly intervals 781min 6
20260209120203G1AAK-1>APSN01,TCPIP*,qAC,T2TEXAS:=5322.35N/00243.42W-231/000/A=000113Beacon on hourly intervals 841min 6
20260209130206G1AAK-1>APSN01,TCPIP*,qAC,T2DALLAS:=5322.35N/00243.42W-231/000/A=000089Beacon on hourly intervals 901min 6
20260209140209G1AAK-1>APSN01,TCPIP*,qAC,T2CAWEST:=5322.35N/00243.42W-231/000/A=000093Beacon on hourly intervals 961min 6
20260209150212G1AAK-1>APSN01,TCPIP*,qAC,T2MCI:=5322.35N/00243.41W-298/000/A=000101Beacon on hourly intervals 1021min 6
20260209160215G1AAK-1>APSN01,TCPIP*,qAC,T2BC:=5322.35N/00243.42W-298/000/A=000090Beacon on hourly intervals 1081min 6