APRS Packet Errors for KO7W-13 (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
20260313061946KO7W-13>APDW16,TCPIP*,qAC,FOURTH:!0000.00N/00000.00EY000/000BajaBlast
20260313064950KO7W-13>APDW16,TCPIP*,qAC,SEVENTH:!0000.00N/00000.00EY000/000BajaBlast
20260313071953KO7W-13>APDW16,TCPIP*,qAC,SECOND:!0000.00N/00000.00EY000/000BajaBlast
20260313074957KO7W-13>APDW16,TCPIP*,qAC,SEVENTH:!0000.00N/00000.00EY000/000BajaBlast
20260313082000KO7W-13>APDW16,TCPIP*,qAC,EIGHTH:!0000.00N/00000.00EY000/000BajaBlast
20260313085003KO7W-13>APDW16,TCPIP*,qAC,FOURTH:!0000.00N/00000.00EY000/000BajaBlast
20260313092007KO7W-13>APDW16,TCPIP*,qAC,THIRD:!0000.00N/00000.00EY000/000BajaBlast
20260313095011KO7W-13>APDW16,TCPIP*,qAC,FOURTH:!0000.00N/00000.00EY000/000BajaBlast
20260313102014KO7W-13>APDW16,TCPIP*,qAC,SECOND:!0000.00N/00000.00EY000/000BajaBlast
20260313105017KO7W-13>APDW16,TCPIP*,qAC,SECOND:!0000.00N/00000.00EY000/000BajaBlast
20260313112021KO7W-13>APDW16,TCPIP*,qAC,FIRST:!0000.00N/00000.00EY000/000BajaBlast
20260313115025KO7W-13>APDW16,TCPIP*,qAC,SEVENTH:!0000.00N/00000.00EY000/000BajaBlast