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
20260409194629OK5TVR-5>APRS,qAS,OK1RPL-15:!4947®³°Î711.40E_000/007g012t044r000p000P...h39b10131L0 WX-lora by OK5TVR DR:-121 DS:-18.75
20260409201631OK5TVR-5>APRS,qAO,OK1CTR-10:!4±47.ôN4131742g200/006g012t043r000p000P...h42b10132Œ<à›T-lorñ)ké°FK6gVQ
20260409204634OK5TVR-5>APRS,qAO,OK1CTR-10:!4?27(38N/01317.40E_000/005g009t041r000p000P...h44b10133L0 WX-lorñ!òy)NK5TVR
20260409204634OK5TVR-5>APRS,qAS,OK1RPL-15:!;,38N/01317.40E_000/005g009t041r000p000P...h44b10133L0 WX-lora by OK5TVR DR:-121 DS:-19.75
20260409224521OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.“8N/01317.40E_000/004g009t038r000p000P...h50"14136L0 WX-lora by OK5TVR
20260409231524OK5TVR-5>APRS,qAS,OK1RPL-15:!49ps*38N/01317.40E_315/004g008t039r000p000P...h47b10124L0 WX-lora by OK5TVR DR:-121 DS:-19.50
20260410001527OK5TVR-5>APRS,qAO,OK1CTR-10:!4947¾38G/01317.40E_315/006g010t038r000p000P...h48b10125L0 WX-lora by OK5TVR
20260410003030OK5TVR-5>APRS,qAS,OK1RPL-15:!49ô7"38N/01317.40E_000/004g008t038R03p300P...h51b10125L0 WX-lora by OK5TVR DR:-121 DS:-18.75