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
20251208085529OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_180/00 g003t051r000p000P...h100b10104L41 WX-lora by OK5TVR
20251208085529OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_180/00 g003t051r000p000P...h100b10104L41 WX-lora by OK5TVR DS -11.50 RS -113
20251208092530OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_135/00 g001t052r000p000P...h98b10103L46 WX-lora by OK5TVR
20251208092530OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g001t052r000p000P...h98b10103L46 WX-lora by OK5TVR DS -12.75 RS -114
20251208094033OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.40E_135/00 g001t052r000p000P...h98b10103L29 WX-lora L{dU
20251208094033OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_135/00 g001t052r000p000P...h98b10103L29 WX-lora by OK5TVR
20251208094033OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_135/00 g001t052r000p000P...h98b10103L29 WX-lora by OK5TVR DS -11.25 RS -115
20251208095532OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.0L/9131w.40E_135/00TROs7_٬?bzpF@r/3sPX-lora by OK5TFR
20251208104037OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/p36/""@ag
20251208111039OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/`4
20251208115542OK5TVR-5>APRS,qAR,OK1KUN-2:!4947S8N#61317.40E_135/002g0P5t056r000p000P...h95b10101L44 WX-lora by OK5TVR