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
20251128030043OK5TVR-5>APRS,OK1JRA-15*,qAO,OK1CTR-10:!494?30&g]#E4f20t023r000p0p3P...h97b10188L0 WX-lora by OK5TVR
20251128033044OK5TVR-5>APRS,OK1JRA-15*,qAO,OK1CTR-10:!4947.38N/01317.0E270/000g000t023r000p003P...h96b10178L0 WX-lo)by)KyXR
20251128043043OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/037X)6C:00g000t023r000p003P...h97b10178L0 WX-lora by OK5TVR
20251128054942OK5TVR-5>APRS,OK1JRA-15*,qAO,OK1CTR-10:!4940hx/01317.40E_270/000g000t024ry02R...h97b101g7Ie%RP-lgza by K5X
20251128060439OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_135/00 g003t024r000p000P...h99b10177L0 WX-lora by OK5TVR
20251128060439OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g003t024r000p000P...h99b10177L0 WX-lora by OK5TVR DS -9.75 RS -114
20251128060443OK5TVR-5>APRS,OK1JRA-15*,qAS,OK1RPL-15:!4947.38N/01317.40E_135/00 g003t024r000p000P...h99b10177L0 WX-lora by OK5TVR DR:-118 DS:1.50
20251128060444OK5TVR-5>APRS,OK1JRA-15*,qAS,OK1JRA-16:!4947.38N/01317.40E_135/00 g003t024r000p000P...h99b10177L0 WX-lora by OK5TVR DS 11.50 RS -40
20251128060444OK5TVR-5>APRS,OK1JRA-15*,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g003t024r000p000P...h99b10177L0 WX-lora by OK5TVR DS -7.25 RS -115
20251128070451OK5TVR-5>APRS,OK1JRA-15*,qAO,OK1CTR-10:!4947.%:;="0