APRS Packet Errors for NB9M-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
20260209131425NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209134425NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209141425NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209144425NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209151425NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209154425NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209161426NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209164426NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209171426NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209174426NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209181426NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN
20260209184426NB9M-1>APIN21,TCPIP*,qAC,T2CAWEST:!3923.56N/08615.30W#MORGANTOWN_IN