APRS Packet Errors for GB2GP (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
20260209132054	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209135056	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209142057	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209145059	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209152101	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209155103	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209162104	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209165106	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209172108	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209175110	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209182111	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct
20260209185113	M0BPQ-1>APMI04,TCPIP,qAS,M0BPQ:;GB2GP 111111z5138.89N/00000.07W, JOTA 20/21 Oct