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
20250806081817OK5TVR-5>APRS,qAO,OK1VP-10:!4947.39N.11317.40U^222/00k=
20250806100044OK5TVR-5>APRS,OK5TVR-17*,qAR,OK1KUN-2:!4947$98.%0131.X%u5::?g011t067r000p001P...h54b10177L113 WX-lora by OK5TVR
20250806101746OK5TVR-5>APRS,qAR,OK1KUN-2:!8=4NS>(O61317> UN222/p03g005t067r90p001P.n`10r1 176L96 WX-lora by OK5TVR
20250806103449OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.0ES>70/00"g014t68r000p001P...h56b10176L218 WX-lora by OK5TVR
20250806114310OK5TVR-5>APRS,OK5TVR-17*,qAR,OK1KUN-2:!4947.38N/01317.40E_180/7e34t071r000p011P...h45b10164L307 WX-lora by OK5TVR
20250806125127OK5TVR-5>APRS,OK5TVR-17*,qAO,OK1CTR-10:!4945"/01317.40E_18e*004g010t074r000p001P...h44b10162L254 WX-lora by OK5TVR
20250806130824OK5TVR-5>APRS,qAO,OK1VP-10:!0}tw.38N/01317.40E_270/003g010t075r000p001P...h45b10161L238 WX-lora by OK5TVR