APRS Packet Errors for KB9LEB (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
20260209104554KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209111555KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209114556KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209121557KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209124558KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209131559KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209134600KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209141601KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209144602KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209151603KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209154604KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB
20260209161605KB9LEB>APX222,TCPIP*,qAC,T2CAEAST:=2901.45N/08058.73Wy73 FROM JACK IN NSB