APRS Packet Errors for IT9AOO-20 (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
20260208182945IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208190000IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208193015IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208200030IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208203045IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208213116IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208220131IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208223146IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208230204IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260208233219IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394
20260209000236IT9AOO-20>APRSGW,TCPIP*,qAR,IT9AOO-20:!3808.31N/01318.63E#MeshCom Test#IT9AOO-20/B=100/A=000394