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
20261011201826OK5TVR-12>APZ023,qAS,OK1BIL-2:!4939/50 *0d8?Q8u.i
20261011203326OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.50N/01349.12E_..>?/f...t040r000p00`Uee`h82b10136 LoRa SHT21 BMP180 QNH
20261011210326OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.50N/01349.12E_.../.+~g...t039r000p000P000h82b10140 LoRa SHT21 BMP180 QNH
20261011211826OK5TVR-12>APZ023,qAR,OK4MD-13:!4939.5QYnQ6E_..NIx(~d...t039r0
20261011231827OK5TVR-12>APZ023,qAR,OK5TVR-15:!4939.50N/01349.12E_.../..,g...t039r000p000P000h80b10151 LoRa SHT21 BMP180 QNH