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
20260411070050OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.<°E_270/002g004t037r000p0015P...h100b10136L46 WX-lora by OK5TVR
20260411084602OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_315/00 g003t040r000p0015P...h99b10134L76 WX-lora by OK5TVR
20260411091603OK5TVR-5>APRS,qAO,OK1CTR-10:!4945.o8Næ<1317.40E_270/002g003t043r000p0015P...h94b10121L97 WX-lora by OK5TVR
20260411101610OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.28/01317NT0%o0Q3/009g012t047r000p DR:-121 DS:-21.25
20260411114746OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.<8E×000/010g017t051r000p000P...h76b10105L307 WX-lora by OK5TVR