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
20251207104620OK5TVR-5>APRS,qAO,OK1VP-10:!4YT7.38N/01317.40E_180/001g002t046r000p005P...h95b10066L36 WX-lora by OK5TVR
20251207124627OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_180/00 g001t048"000p005P...h92b10065L39 WX-lora by OK5TVR
20251207124627OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g001t048r000p005P...h92b10065L39 WX-lora by OK5TVR
20251207124627OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g001t048r000p005P...h92b10065L39 WX-lora by OK5TVR DS -11.75 RS -113
20251207141635OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_090/00 g00 t047r000p005P...n?5b1006µM5 ßP-lora by OK5TVR
20251207141635OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_090/00 g00 t047r000p005P...h93b10065L4 WX-lora by OK5TVR
20251207141635OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_090/00 g00 t047r000p005P...h93b10065L4 WX-lora by OK5TVR DS -10.50 RS -114
20251207153138OK5TVR-5>APRS,qAO,OK1VP-10:!494708N,3;317.40E_180/000g000t046r000p005P...h95b10077L0 WX-lora by OK5TVR
20251207160138OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g001t045r000p005P...h95b10077L0 WX-lora by OK5TVR
20251207160138OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g001t045r000p005P...h95b10077L0 WX-lora by OK5TVR DS -10.75 RS -114