APRS Packet Errors for SR2ST-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
20260208131938	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208134938	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208141938	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208144938	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208151938	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208154938	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208161939	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208164939	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208171939	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208174939	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208181939	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367
20260208184939	SR2ST-12>APRSGW,TCPIP*,qAR,SR2ST-12:!5309.86N/01754.87E#MeshCom 433.175MHz/A=000367