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
20251206073055OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_135/00 g001t034r000p004P...h100b10086L4 WX-lora by OK5TVR
20251206073055OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g001t034r000p004P...h100b10086L4 WX-lora by OK5TVR DS -10.00 RS -114
20251206090104OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.»8F/01317.40E_090/001g004t033r000p004P...h100b10076L15 WX-lora by OK5TVR
20251206110115OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g001t034r000p004P...h100b10065L24 WX-lora by OK5TVR
20251206110115OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g001t034r000p004P...h100b10065L24 WX-lora by OK5TVR DS -10.75 RS -114
20251206123123OK5TVR-5>APRS,qAO,OK1CTR-10:!2_47(38N/0317.4
20251206124626OK5TVR-5>APRS,qAO,OK1CTR-10:! 6½k°–si‘r»J¸o`é‰27LwvEX> Âè«Ç~0%—0Ú®t>nN1b101L7 TX-lora by OC½VR
20251206124626OK5TVR-5>APRS,qAO,OK1CTR-10:! 6½k°–si‘r»J¸o`é‰27LwvEX> Âè«Ç~0%—0Ú®t>nN1b101L7 TX-lora by OC½VR