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
20250830191521OK5TVR-5>APRS,qAO,OK1VP-10:!49.38N/01317.40E_270/000g00 aa4v32t~200P...h86b10058L0 WX-lora€by‰O_uÔVÂ
20250830193224OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g003t057r000p000P...h87b10069L0 WX-lora by OK5TVR
20250830193228OK5TVR-5>APRS,OK5TVR-17*,qAS,OK1RPL-15:!4947.38N/01317.40E_222/00 g003t057r000p000P...h87b10069L0 WX-lora by OK5TVR DR:-121 DS:-11.00
20250830200635OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.#N 01317.40E_222/000g000t056rV:
20250830222305OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.»0F¯81317.40E_222/000g000t052r000p000P.N.h?Xd10072L0 WX-lora by OK5TVR