APRS Packet Errors for SM4FYX-12 (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
20260209091851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=008/A=000656
20260209094851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=006/A=000656
20260209101851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209104851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209111851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209114851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209121851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209124851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209131851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209134851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=007/A=000656
20260209141851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260209144851SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=007/A=000656