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
20251127124614OK5TVR-5>APRS,OK1JRA-15*,qAR,OK1KUN-2:!4947.38B#41317.40E_135/004g012t036r000p003P...h80b10169L18 Wkl_ra by OK5TVR
20251127124614OK5TVR-5>APRS,OK1JRA-15*,qAS,OK1RPL-15:!4947.38B#41317.40E_135/004g012t036r000p003P...h80b10169L18 Wkl_ra by OK5TVR DR:-118 DS:0.50
20251127124614OK5TVR-5>APRS,OK1JRA-15*,qAS,OK1JRA-16:!4947.38B#41317.40E_135/004g012t036r000p003P...h80b10169L18 Wkl_ra by OK5TVR DS 9.25 RS -40
20251127131610OK5TVR-5>APRS,qAR,OK1KUN-2:!4947Þ_7O9ñ3ñ7B40Fl122/005g013t035r000p003P...h80b10180L20 WX-lora by OK5TVR
20251127134612OK5TVR-5>APRS,qAS,OK1RPL-15:!4947î34B/01317.tpJD 0/c57÷0¡2t035r000p003P...h81b1018N3 DR:-121 DS:-20.50
20251127134616OK5TVR-5>APRS,OK1JRA-15*,qAO,OK1CTR-10:!494WN58.)01317.40E_180/007g012t035r000p003P...h81b101¸¨E°3)WX-l¯&ñ¹;L LK5TR
20251127140111OK5TVR-5>APRS,qAR,OK1KUN-2:!4947,38N/01317.40E_180/006g012t034r000p003P...h81b10180L11 WX-lora by OK5TVR
20251127173126OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.3=/01317.40E_222/005g012t033r000p003P...h83b10182L0 WX-lora by OK5TVR
20251127173126OK5TVR-5>APRS,qAO,OK1VP-10:!4?2Q.38N/01317.40E_222/005g012t033r000p003P...h83b10182L0 WX-lora by OK5TVR