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
20260201114559OK5TVR-5>APRS,qAS,OK1PNK-10:!43>7.38N/01317.40E_000/006g008t032r000p0038P...h9524``67L42 WX-lora by OK5TVR DS -20.50 RS -113
20260201123104OK5TVR-5>APRS,qAO,OK1VP-10:!4947.c8N/01317.40E_270/003g006t034r000p0038P...h93b10055L49 WX-lora by OK5TVR
20260201131607OK5TVR-5>APRS,qAO,OK1VP-10:!49<7.38N/01317.40E_270/003g007t034r000p0038P...h93b10055L43 WX-lora by OK5TVR
20260201151614OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317>O5SLU7`e4t032r000p0038P...h97b10056L10 WX-lora by OK5TVR
20260201170123OK5TVR-5>APRS,qAS,OK1RPL-15:!7:74.F01317.4`@500/005g007t031r000p0038P...h99ba0057L0 WX-lorb by K5TVR DR:-121 DS:-20.75