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
20260208151849	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=046/A=000656
20260208154850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208161850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208164850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208171850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208174850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208181850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208184850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208191850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208194850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208201850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656
20260208204850	SM4FYX-12>APRSGW,TCPIP*,qAR,SM4FYX-12:!6020.26N/01545.29E-MesCom Gate/B=100/A=000656