APRS Packet Errors for IR5ZYS-7 (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
20260208182736IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208185734IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208195735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208202735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208205734IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208212736IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208215735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208222735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208225735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208232735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24
20260208235735IR5AR-C>APU25N,TCPIP*,qAC,APRSC33:;IR5ZYS-7 *041600z4403.45N/01107.66E7RETE-UHF-V.B.-RPTR-LIK-H24