APRS Packet Errors for WB0HTW (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
20260208142229WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u+-!!Craspian 64 / SSD
20260208145230WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u+-!!Craspian 64 / SSD
20260208152231WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u+-!!Craspian 64 / SSD
20260208155232WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u!-!!Craspian 64 / SSD
20260208162233WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u(-!!Craspian 64 / SSD
20260208165234WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u+-!!Craspian 64 / SSD
20260208172235WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u.-!!Craspian 64 / SSD
20260208175236WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uL;7u.-!!Craspian 64 / SSD
20260208182237WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u+-!!Craspian 64 / SSD
20260208185238WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u+-!!Craspian 64 / SSD
20260208192239WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u.-!!Craspian 64 / SSD
20260208195240WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLT7u4-!!Craspian 64 / SSD