APRS Packet Errors for IW0UTD-17 (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
20260208203953IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260208211008IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260208214024IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260208221040IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260208224055IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260208231110IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260208234125IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260209001140IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260209004155IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260209011210IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190
20260209014225IW0UTD-17>APRSGW,TCPIP*,qAR,IW0UTD-17:!3954.22N/00835.94E#Meshcom#Iw0utd-17/B=100/A=000190