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
20251019143342OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/0¡317.40E_135/001g004t051Bšš à:00P...h53b10104L15 WX-lora by OK5TVR
20251019160349OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_270/00 g002t046r000p000P...h65b10107L1 WX-lora by OK5TVR
20251019160349OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_270/00 g002t046r000p000P...h65R20104L1 WX-lora by OK5TVR
20251019160349OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_270/00 g002t046r000p000P...h65b10107L1 WX-lora by OK5TVR DS -10.00 RS -113
20251019160353OK5TVR-5>APRS,OK5TVR-17*,qAR,OK1KUN-2:!4947.38L/01317.40E_270/00 g002t046r000p000P...h65b10107L1 WX-lora by OK5TVR
20251019160353OK5TVR-5>APRS,OK5TVR-17*,qAS,OK1RPL-15:!4947.38N/01317.40E_270/00 g002t046r000p000P...h65b10107L1 WX-lora by OK5TVR DR:-121 DS:-13.75
20251019171855OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/0191—.40E_
20251019173355OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_315/0ð3k<05t045r000p000P..k6d10108L0 WX-lora by OK5TVR
20251019173355OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.4`@_315/003g005t945r60Pp600P..~860W|$.œ.^3Fz7çÎûb by OK5TVR
20251019180355OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.3H01317.40E_000/003g005t045r000p000P...h68¢1ðýð5L0 WX-lora by OK5TVR