APRS Packet Errors for OK5TVR-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
20260112114817OK5TVR-5>APRS,qAS,OK1RPL-15:!>9>7$L01317.` Z13`z`60g000t023r000p000P..45b10125L21 WX-lora by OK5TVR DR:-121 DS:-21.50
20260112130320OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_135/00 g002t026r000p000P...h87b10113L17 WX-lora by OK5TVR
20260112130320OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g002t026r000p000P...h87b10113L17 WX-lora by OK5TVR DS -18.25 RS -116
20260112131821OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_135/00 g001t027r000p000P...h87b10112L12 WX-lora by OK5TVR
20260112131821OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g001t027r000p000P...h87b10112L12 WX-lora by OK5TVR DS -19.00 RS -116
20260112140323OK5TVR-5>APRS,qAS,OK1RPL-15:!494730D%:1317.40E_135/000g000t026r000p000P...h88b018|5WxmL 2g by OK5TV DR:-121 DS:-21.50
20260112143326OK5TVR-5>APRS,qAO,OK1CTR-10:!%9$?3Ny17W.40E_135/000g00x025~000p0Цv{=lfb10115L3@Wh_lB9Ǔ
20260112161836OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g001t026r000p000P...h99b10103L0 WX-lora by OK5TVR
20260112163336OK5TVR-5>APRS,qAS,OK1RPL-15:!6;45.38N/01317.40E_Q3/tH ܋