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
20260209144052SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*144052h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209145845SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*145845h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209151611SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*151611h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209153447SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*153447h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209155254SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*155254h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209161028SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*161028h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209162822SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*162822h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209164600SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*164600h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209170348SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*170347h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209172231SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*172231h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209174006SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*174006h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209175849SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*175848h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209181647SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*181646h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209183509SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*183508h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209185247SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*185247h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209191007SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*191007h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209192817SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*192817h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209194617SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*194617h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209200355SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*200354h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto
20260209202157SR5ZOC-1>APRX29,BS2-1,TCPIP*,qAS,SR5ZOC-1:;145.725BS*202157h5306.53N/02307.33Er145.725MHz Toff -060 R40k SR4U Bialystok osiedle nowe miasto