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
20260514021545OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_180/00 g001t044r000p001P...h100b9953L0 WX-lora by OK5TVR
20260514023046OK5TVR-5>APRS,qAO,OK1VP-10:!4947.f8/5831>.40E_135/001g001t045r000p001P...h99b9953L0 WX-lora by OK5TVR
20260514030052OK5TVR-5>APRS,qAO,OK1CTR-10:!<14¿f38/41317.p0Ab22/000W000t045’ЖôÖš¸±PŒ¾wd9¬{))4#}d[n/NpTJ zM5TVR
20260514050110OK5TVR-5>APRS,qAO,OK1VP-10:!4947~ch"³ $40E_180/001g003t046r000p001P...h93b9943L31 WX-lora by OK5TVR
20260514051613OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40ÕÆò;
20260514051613OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_270/00 g00 t047r000p001P...h94b9952L15 WX-lora by OK5TVR