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
20260208201709SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208204711SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208211714SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208214716SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208221718SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208224721SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208231723SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260208234726SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209001728SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209004731SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209011733SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin
20260209014736SR8BBS-5>ID,qAR,SR1NRE:!5113.41N/02231.73EI JNOS 2.0i AMPRNet 44.165.129.250 Lublin