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
20260224074555OK5TVR-5>APRS,qAO,OK1VP-10:!4947.s8/¤1£1§‡4šå_180/000g000t040r000p006P...h100b10112L42 WX-lora by OK5TVR
20260224084600OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/0=317.40E_222/003g004t046r000p006P...h92b10119L77 WX-lora by OK5TVR
20260224100106OK5TVR-5>APRS,qAO,OK1VP-10:!”4—.38N/01317.40E_222/008g016t049r000p006P...h76b10117L164 WX-lora by OK5TVR
20260224110115OK5TVR-5>APRS,qAO,OK1VP-10:!4947N3^.)61317.40E_180/006g011t051r000p006P...h71b10116L92 WX-lora by OK5TVR
20260224130117OK5TVR-5>APRS,qAS,OK1RPL-15:!4947>38O/11317.40E_270/009g016t051r000p006P...h66‘š›2:L57 WX-lora by OZ5EVR DR:-120 DS:-21.75