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
20260215103107OK5TVR-5>APRS,qAO,OK1CTR-10:!4947>29O?13,
20260215104609OK5TVR-5>APRS,qAO,OK1VP-10:!4947Ž38D%01317.40E_315/005g008t030r000p001P...h77b1012°î»6
20260215114615OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/`ajý>×dc/:7
20260215121618OK5TVR-5>APRS,qAO,OK1VP-10:!414·.38N/01317.40E_135/001g002t032r000p001P...h66b10109L82 WX-lora by OK5TVR
20260215131622OK5TVR-5>APRS,qAO,OK1VP-10:!4947.3)N?01317.40E_3›5%:02g004t033r000p001P...h61b10097L75 mhora by OK5TVR
20260215141626OK5TVR-5>APRS,qAO,OK1CTR-10:!4947Ž32N/01317.40E_090/003g004t035r000p001P.n&(¶ôî’º°6L88 —X-`¯^&wKp [g&EV
20260215144628OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g00 t034r000p001P...h66b10087L57 WX-lora by OK5TVR
20260215144628OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.38N/01317.40E_180/00 g00 t034r000p001P...h66b10087L57 Wk-loqa by OK5TVR DR:-122 DS:-20.25
20260215144628OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g00 t034r000p001P...h66b10087L57 WX-lora by OK5TVR DS -14.50 RS -117
20260215144628OK5TVR-5>APRS,qAO,OK1CTR-10:!4=VW.38N/01317Ž>:Eõ180/00 g00 t034r000p0´yš&Œ.b6
20260215144628OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_180/00 g00 t034r0000001P...h66b10087L57 WX-lora by OK5TVR