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
20260604012037OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g002t048r000p000P...h100b10044L0 WX-lora by OK5TVR
20260604015041OK5TVR-5>APRS,qAO,OK1VP-10:!4947®38N/01317.40E_180/000g000t048r000p000P...h99b10044L0 WX-lora by OK5TVR
20260604045101OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_090/00 g003t054ò0˜’Z:00P...h97b10040L47 WX-lora by OK5TVR
20260604045101OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_090/00 g003t054r000p000P...h97b10040L47 WX-lora by OK5TVR
20260604050603OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_090/00 g001t055r000p000P...h92b10039L31 WX-lora by OK5TVR
20260604052105OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_135/00 g002t054r000p000P...h99b10041L34 WX-lora by OK5TVR
20260604055107OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_090/00 g002t057r000p000P...h88b10038L88 WX-lora by OK5TVR
20260604070612OK5TVR-5>APRS,qAO,OK1VP-10:!4947.3ø‚/<1317.40E_270/002g004t064r000p000P...h75b10023L116 WX-lora by OK5dP