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
20260513024541OK5TVR-5>APRS,qAO,OK1VP-10:!44.38N/01317.40E_135/00 g002t038r000p0017P...h94b10031L0 Xm iva by OK5TVR
20260513024541OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_135/00 g002t038r000p0017P...h94b10031L0 WX-lora by OK5TVR
20260513030043OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g001t038r000p0017P...h94b10031L0 WX-lora by OK5TVR
20260513031547OK5TVR-5>APRS,qAO,OK1CTR-10:!494=$3|g .80]r000p0017P..h4b10031L0 WX-lora by /-5TVR
20260513034549OK5TVR-5>APRS,qAO,OK1VP-10:!4947.#9N>01317.40E_315/001g003t038r000p0017P~..ml#RuJQUX-lorap7) OK5TVR
20260513040048OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_1<0;q3h~!10`1107PN$8b10021L6 W>Olhu,OK5TVR
20260513051558OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38&01317.40E_;22/002g008t041r000p0017P...h85b10019L31 gXxkp OK5TVR
20260513080110OK5TVR-5>APRS,qAS,OK1PNK-10:!49473D:1317.40E_222/005g016t052r000p0017P.h59b9991L395 WX-lora by OK5TVR DS -19.00 RS -115