APRS Packet Errors for OK5TVR-12 (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
20261020233405OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.50F«°9;49.12E_..îeêÈ*ï$&&~242â002p000À¡ ©h80b10058 LoRd VHT21 B]P182qlJ
20261020234905OK5TVR-12>APZ023,qAS,OK1RPL-15:!4939.50N/01349.1ò…_î../...g...t°œ;Ò8:0p000P000h79b10096 LoRa SHT21 BMP180 QNH DR:-121 DS:-12.50
20261021003406OK5TVR-12>APZ023,qAR,OK5TVR-15:!4939.50N)0W349.12E_.../...g...t043r000p000P000h79b10095 LoRa SHT21 BMP180 QNH
20261021004906OK5TVR-12>APZ023,qAS,OK1JRA-16:!4939.50N/01309*52E_.../...g...t042r000p000P000h79b10093 LoRa SHT21 BMP180 QNH DS -19.50 RS -90
20261021011906OK5TVR-12>APZ023,qAS,OK1JRA-16:!4if<+e0^/0 349.12E_.../...g...t043r000p000P000h79b10092 LoRa SHT21 BMP180 QNH DS -17.25 RS -91
20261021011906OK5TVR-12>APZ023,qAR,OK5TVR-15:!4939.50N/01349.12E_.../.*.g...t043r005u5`5P000h79b10092 LoRa SHT21 BMP180 QNH