APRS Packet Errors for SP4SR-9 (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
20260209121656SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209124711SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209131726SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209134741SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209141806SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209144811SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209151827SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209154842SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209161857SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209164913SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554
20260209171928SP4SR-9>APRSMC,TCPIP*,qAR,SP4SR-10:!5343.59N/02028.76E>#SP4SR/B=100/A=000554