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
20260512190229OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g002t044r000p0017P...h75b10048L0 WX-lora by OK5TVR
20260512200233OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g004t042r000p0017P...h79b10049L0 WX-lora by OK5TVR
20260512201733OK5TVR-5>AXZS,qAO,OK1VP-10:!4947t01317(40E_180/00 g002t042r8044лq&x8W0t,I uSX-lora byK5TVR
20260512201733OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g002t042r000p0017P...h80b10049L0 WX-lora by OK5TVR
20260512210239OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g002t040r000p0017P...h86b10051L0 WX-lora by OK5TVR
20260512213241OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/ (20/40E_180/002g004t039r000p0012Pnj*,|7b10051L0 WX-lok ylY$fǗ
20260512230019OK5TVR-5>APRS,qAO,OK1VP-10:!2?27.38N/01317.40E_222/001g004t040r000p0017P...h84b10041L0 WX-lora by OK5TVR
20260513000023OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.1ji01317.40E_315/000g000t037r000p0017P...h93b10042L0 WX-lora by OK5TVR DS -20.75 RS -114