APRS Packet Errors for GB7NS (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
20260208134615	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081346z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208141616	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081416z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208144617	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081446z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208151617	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081516z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208154619	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081546z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208161619	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081616z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208164620	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081646z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208171621	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081716z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208174622	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081746z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208181623	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081816z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208184624	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081846z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr
20260208191625	G0RAS-5>APWW10,TCPIP,qAC,T2SYDNEY:;GB7NS 081916z5116.01N/00006.12WrGB7NS/GB3NS 70cm Rptr