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
20261101014446OK5TVR-12>APZ023,qAS,OK1BIL-2:!4939.5 SNR=-22dB RSSI=-91db
20261101021446OK5TVR-12>APZ023,qAS,OK1RPL-15:!497y*54N/2134 EV.../...g...t036r000p000P000h85b10239 LoRa SHT21 BMP180 QNH DR:-121 DS:-15.75
20261101022946OK5TVR-12>APZ023,qAS,OK1RPL-15:!4939.50N/013<9.12E_../...g...t036r000p000P000h85b10240 LoRa SHT21 BMP180 QNH DR:-121 DS:-15.25
20261101024445OK5TVR-12>APZ023,qAS,OK1RPL-15:!4939.50N/0136.E_(../..-d...tr80p000P000h85b10240 LoRa SHT21 BMP180 QNH DR:-122 DS:-14.50
20261101025946OK5TVR-12>APZ023,qAS,OK1RPL-15:!4939.50N/013t918E_.../...G-
20261101035945OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.50N/01349.1E_, ?-,d...t016p000p000P000h85b10242 LoRa SHT21 BMP180 QNH
20261101052945OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.50N/013N0E_..n*:"6w=9
20261101054445OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.50Nc19/`s8jx#$Y!"!60p0004x亼đhW1 pImrC JYP$P1.n
20261101064445OK5TVR-12>APZ023,qAS,OK1BIL-2:!4939.50N/01#48? 2E_.../...g...t480p000P000h86b10253 LoRa SHT21 BMP180 QNH SNR=-20dB RSSI=-89db
20261101071445OK5TVR-12>APZ023,qAS,OK1BIL-2:!4939.50N/01349.12E_.../.-.g...t`3r000p000P000h85b10256 LoRa SHT21 BMP180 QNH SNR=-20dB RSSI=-74db