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
20251210090056OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_090/00 g00 t041r000p001P...h100b10143L35 WX-lora by OK5TVR
20251210090057OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_090/00 g00 t041r000p001P...h100b10143L35 WX-lora by OK5TVR DS -13.75 RS -111
20251210110109OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_135/00 g001t051r000p001P...h85b10136L46 WX-lora by OK5TVR
20251210110109OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g001t051r000p001P...h85b10136L46 WX-lora by OK5TVR DS -9.50 RS -115
20251210123115OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_990/0°9k¸02t054q000p001P...h81b10133L40 WX-lora by OK5TV^
20251210130118OK5TVR-5>APRS,qAO,OK1VP-10:!2•ø÷BSXNI`R5RQ+40E_180/004g005t053r000p001P...h82b10135L18 WX-lora by OK5TVR
20251210141624OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_090/00 g001t052r000p001P...h85b10135L10 WX-lora by OK5TVR
20251210141625OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_090/00 g001t052r000p001P...h85b10135L10 WX-lora by OK5TVR DS -11.25 RS -115