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
20260209102309WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u(-!!Craspian 64 / SSD
20260209105310WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u+-!!Craspian 64 / SSD
20260209112311WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u1-!!Craspian 64 / SSD
20260209115312WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uL;7u+-!!Craspian 64 / SSD
20260209122313WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u!-!!Craspian 64 / SSD
20260209125314WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u+-!!Craspian 64 / SSD
20260209132315WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLN7u+-!!Craspian 64 / SSD
20260209135316WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u1-!!Craspian 64 / SSD
20260209142317WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLT7u+-!!Craspian 64 / SSD
20260209145318WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u(-!!Craspian 64 / SSD
20260209152319WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLG7u+-!!Craspian 64 / SSD
20260209155320WB0HTW>APX216,TCPIP*,qAC,T2NL:=/:uLA7u(-!!Craspian 64 / SSD