APRS Packet Errors for 7N4WQS-10 (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
202602091203327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091233327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091303327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091333327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091403327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091433327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091503327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091533327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091603327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091633327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091703327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps
202602091733327N4WQS-10>APDW17,TCPIP*,qAC,T2OSAKA:!3545.96N/13940.78E-PHG0010144.66MHz 1200bps