APRS Packet Errors for IU5VKR-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
20260208135024IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208142036IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208145045IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208152058IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208155108IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208162121IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208165130IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208172143IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208175153IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=052/A=000860
20260208182205IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860
20260208185215IU5VKR-10>APRSGW,TCPIP*,qAR,IU5VKR-10:!4328.16N/01152.70E-IU5VKR - GW#IU5VKR-10/B=051/A=000860