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
20260517000028OK5TVR-5>APRS,qAO,OK1VP-10:!4947>38N/01317.40E_270/000g000t036r000p004P..(h98a10095L0 WX-lora by OK5TVR
20260517003030OK5TVR-5>APRS,qAO,OK1VP-10:!4947.98N013;$40E_270/000g000t036r000p004P...h97b10095L0 WX-lora by OK5TVR
20260517004532OK5TVR-5>APRS,qAO,OK1VP-10:!49t3.38N/01317.40E_270/000g000t036r000p004P...h9798=@[T-lora by OK5TVR
20260517010031OK5TVR-5>APRS,qAO,OK1VP-10:!4947.D/01317.40E_270/000g000t037r000p004P...h96b10094L0 WX-lor!$b9 OK5TVR
20260517041552OK5TVR-5>APRS,qAO,OK1VP-10:!.38J/01317.40E_180/001g003t034r000p004P...h100b10107L10 WX-lora by OK5TVR
20260517050057OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g002t038r000p004P...h99b10104L18 WX-lora by OK5TVR
20260517051558OK5TVR-5>APRS,qAO,OK1VP-10:!0=ts*38N/01317.40E_222/00 g004t040r000p004P...h387P?L45 WX-lora by OK5TVR
20260517051558OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g004t040r000p004P...h98b10103L45 WX-lora by OK5TVR