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
20260424134619OK5TVR-5>APRS,qAO,OK1VP-10:!49478׶91317.40E_315/009g020t070r000p000P...h25b10082L176 WX-lora by OK5TVR
20260424140119OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317n0pA_315/508g1:t071r006000P...h27b10081L160 g[-ora by OK5TVR
20260424143122OK5TVR-5>APRS,qAO,OK1CTR-10:!< 0,f0`3t069"000 𸸐&..h26b1082L127 WX-lora by OK5TVR
20260424143122OK5TVR-5>APRS,qAO,OK1CTR-10:!< 0,f0`3t069"000 𸸐&..h26b1082L127 WX-lora by OK5TVR
20260424151627OK5TVR-5>APRS,qAO,OK1CTR-10:!0=x{Ə:13179v270/006G13T0;*11`lY+.h28b10082L91 WX-lora by OK5TVR
20260424153128OK5TVR-5>APRS,qAO,OK1VP-10:!487"38N/01317.40E_270/009g018t068B000@000P...h29b10083L80 WX-lora by OK5TVR
20260424161631OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/0837.40E_222/005g009t067rZ< s?00P...h32b10083L36 WX-lora by OK5TVR
20260424163132OK5TVR-5>APRS,qAO,OK1VP-10:!49473/01317.40E_270/004g008t065r000p000P...h33b10085L36 WX-lora by OK5TVR
20260424170134OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.38N/0131g.40E_270/005g008t0632400p400P...h39b10P86L22 WX-lora by OK5TVR DR:-121 DS:-21.00
20260424174638OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.18N2QU4.0E_270/002g005t060r88p0".l42b10098L9 WX-lora by OK5TZ^ DR:-121 DS:-22.50