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
20250630215315OK5TVR-5>APRS,qAS,OK5TVR-15:!4947.38N/01317.40E_270/00 g002t064r000p000P...h57b10138L0 WX-lora by OK5TVR DS 9.50 RS -40
20250630231834OK5TVR-5>APRS,qAS,OK5TVR-15:!4947.38N/01317.40E_180/00 g003t061r000p000P...h61b10139L0 WX-lora by OK5TVR DS 10.75 RS -40
20250630231835OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g003t061r000p000P...h61b10139L0 WX-lora by OK5TVR
20250701000947OK5TVR-5>APRS,qAS,OK5TVR-15:!4947.38N/01317.40E_180/00 g001t057r000p000P...h69b10131L0 WX-lora by OK5TVR DS 9.75 RS -40
20250701004355OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_270/00 g002t056r000p000P...h76b10142L0 WX-lora by OK5TVR
20250701004355OK5TVR-5>APRS,qAS,OK5TVR-15:!4947.38N/01317.40E_270/00 g002t056r000p000P...h76b10142L0 WX-lora by OK5TVR DS 11.25 RS -40
20250701011802OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.40E_1;0/300g008£11q000p000P..îh7;B3tP $ÿ=Û3!>ÙXß|2