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
20260213001521OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_222/00 g002t039r000p0031P...h99b9822L0 WX-lora by OK5TVR
20260213001522OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_222/00 g002t039r000p0031P...h99b9822L0 WX-lora by OK5TVR DS -15.50 RS -114
20260213024536OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g00 t041r001p0031P...h100b9842L0 WX-lora by OK5TVR DS -13.75 RS -113
20260213024536OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g00 t041r001p0031P...h100b9842L0 WX-lora by OK5TVR
20260213031539OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.40E_180/00 g002t0421i0$..h100b9841L0 WX-lora by OK5TVR
20260213031539OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g002t042r000p0033P...h100b9841L0 WX-lora by OK5TVR DS -13.25 RS -115
20260213031539OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g002t042r000p0033P...h100b9841L0 WX-lora by OK5TVR
20260213041544OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/13.40E_222/001g003t042r000p0035P...h100b9841L0 WX-lora by OK5TVR
20260213043046OK5TVR-5>APRS,qAO,OK1CTR-10:!E=I~0Q317>41dOQ^PI661g002t042r001p0035P...h100b9842L0 WX$_ra by OK5TVR
20260213044549OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317n00A_180/001g002t042r003p0035P...h100b9841L0 WX-lora by OK5TVR