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
20260427141623OK5TVR-5>APRS,qAS,OK1PNK-10:!;4,38N/01317.40uo000/007g012t070r000p000P...h25b10122L161 WX-lora by OK5TVR DS -16.00 RS -115
20260427144630OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_000/00G:806x33p000P...h27b10124L123 WX-lora by OK5TVR
20260427173130OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.3G&01317.40E_000/004g008t058r000p000P...h33b10130L13 WX-lora by OK5TVR DR:-121 DS:-20.75
20260427190133OK5TVR-5>APRS,qAO,OK1VP-10:!49473B#01317.40E_000/006g008t054r000p00:.>k10134L0 WX-lora "} KK5TV2
20260427191635OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_000/0<6t $#r000p000P...h45b10134L0 WX-lora by OK5TVR
20260427194635OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.38}31317.40E_000/003g005t051r000p000P...h48b10135L0 WX-lora by OK5TVR DR:-121 DS:-19.75