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
20260728003030OK5TVR-5>EPRS,qAO,OK1CTR-10:!4947NdB:1317>:E915/000g000t054Ґ:0:00P...h96b20143L0 WX-lora by OK5TVR
20260728023047OK5TVR-5>APRS,qAO,OK1CTR-10:!494w&C$40E_"&715SZ@6~000p000P..hc#s05*]X-lora by OK5T
20260728030052OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g001t054r000p000P...h100b10154L0 WX-lora by OK5TVR
20260728034555OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.40E_2vr/t0mFhnud 
20260728041557OK5TVR-5>APRS,qAR,OK5TVR-15:!4947.38N/01317.40E_270/00 g003t056r000p000P...h97b10152L10 WX-lora by OK5TVR
20260728044558OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_315/00 g002t057r000p000P...h94b10152L18 WX-lora by OK5TVR
20260728051559OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g002t057r000p000P...h95b10152L22 WX-lora by OK5TVR