APRS Packet Errors for SR8BBS-5 (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
20260209091812SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209094815SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209101818SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209104820SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209111822SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209114825SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209121827SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209124830SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209131832SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209134835SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209141837SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209144840SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin