APRS Packet Errors for 145.725BS (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
20260208163634SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*163634h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208165434SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*165434h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208171203SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*171203h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208173018SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*173018h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208174753SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*174753h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208180618SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*180618h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208182443SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*182443h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208184300SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*184300h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208190148SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*190148h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208191933SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*191933h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208193645SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*193645h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208195435SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*195434h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208201208SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*201208h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208202943SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*202943h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208204733SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*204733h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208210513SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*210513h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208212318SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*212318h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208214117SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*214117h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208215843SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*215843h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260208221704SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*221704h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto