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
20260420081559OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_222OV66g012t049r000p0022P...h77b10097L178 WX-lora by OK5TVR
20260420093108OK5TVR-5>APRS,qAS,OK1RPL-15:!494w.3}31317.40E_222/011g019t048r000p0022P..+l76b10098L132#Whlora by OK5TVR DR:-121 DS:-19.75
20260420100110OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.N#:1317.40E_222/010g021t050r000p0022P...h6j105L216 WX-lora by OK5V DR:-121 DS:-21.25
20260420100111OK5TVR-5>APRS,qAO,OK1VP-10:!494.8B/01317.40E_222/010g021t050r000p0022P...h65b10085L216 WX-lora by OK5TVR
20260420101610OK5TVR-5>APRS,qAO,OK1VP-10:!4947m5=31;.40E_180/009g01Wr036t6V60bV-. H6:b10086L87 WX-lora by OK5TVR
20260420101610OK5TVR-5>APRS,qAS,OK1RPL-15:!= >#(N> DR:-121 DS:-21.50
20260420111613OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.38N/0;$40E_222/011g024t053r000p0022P...h60b10083L405 WX-lora by OK5TVR DR:-122 DS:-19.75
20260420121620OK5TVR-5>APRS,qAS,OK1RPL-15:!4947N01317.40E_315/009g01t0p090yXZ."d1b100hcLaf5 WX-lora F)K3TVR DR:-121 DS:-21.50
20260420123121OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.38N/01:=9L_;70/008g016t051r000p0022P...h69b10084L209 WX-lora by OK5TVR DR:-121 DS:-20.00
20260420131626OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_222/0p7c0u3t051rPVPp03#rON.N6b10084L94 WX-lora by OK5TVR DS -20.00 RS -112