APRS Packet Errors for OK1JRA-6 (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
20260416145521OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943qB<1308N73C_302/003g005t068h39b10224r000_B4.14V SNR=-19dB RSSI=-91db
20260416150028OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/090𦾺G㰱2$<3g004t068h38b10224r000_B4.14V SNR=-21dB RSSI=-90db
20260416151546OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12F01308.73E_299/005g007t067h41b10223r000_B4.14V SNR=-20dB RSSI=-90db
20260416154623OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.%2K+308.73E_303/004g007t065h43b10225r000_B4.17V SNR=-21dB RSSI=-90db
20260416160142OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/`135h.73E_307/004g0041>d"00?D2.16V SNR=-21dB RSSI=-91db
20260416160648OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.+&
20260416163219OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.52Jk41308.73E_303/004g005t064h46b10224r000_B4.17V SNR=-21dB RSSI=-86db
20260416171308OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/`135h.73E_310/002g00t6h59b82nv000_B4.17V SNR=-21dB RSSI=-89db
20260416173333OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.9:N/01308.73E_315/001g001t060h51b10225r000_B4.15V SNR=-20dB RSSI=-90db
20260416174851OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/0 2!).73_:15/001g002t059h52b10226r000_B] SNR=-21dB RSSI=-90db