APRS Packet Errors for IZ5FSA-2 (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
20260208163759IZ5FSA-2>APRSMC,TCPIP*,qAR,IK5ZXH-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208170810IZ5FSA-2>APRSMC,TCPIP*,qAR,IU5TRZ-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208172640IZ5FSA-2>APRSMC,TCPIP*,qAR,IW5EIA-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208173825IZ5FSA-2>APRSMC,TCPIP*,qAR,IQ5BL-13:!4345.24N/01110.85E[Meshcom4#Leo
20260208175727IZ5FSA-2>APRSMC,TCPIP*,qAR,IW5EIA-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208180840IZ5FSA-2>APRSMC,TCPIP*,qAR,IK5XMK-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208183915IZ5FSA-2>APRSMC,TCPIP*,qAR,IU5TRZ-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208190910IZ5FSA-2>APRSMC,TCPIP*,qAR,IK5XMK-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208200942IZ5FSA-2>APRSMC,TCPIP*,qAR,IW5EIA-12:!4345.24N/01110.85E[Meshcom4#Leo
20260208203957IZ5FSA-2>APRSMC,TCPIP*,qAR,IQ5BL-13:!4345.24N/01110.85E[Meshcom4#Leo
20260208211059IZ5FSA-2>APRSMC,TCPIP*,qAR,IQ5BL-13:!4345.24N/01110.85E[Meshcom4#Leo
20260208214113IZ5FSA-2>APRSMC,TCPIP*,qAR,IQ5BL-13:!4345.24N/01110.85E[Meshcom4#Leo
20260208221100IZ5FSA-2>APRSMC,TCPIP*,qAR,IR5AY-12:!4345.24N/01110.85E[Meshcom4#Leo