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
20260517051558OK5TVR-5>APRS,qAO,OK1VP-10:!0=ts*38N/01317.40E_222/00 g004t040r000p004P...h387P?L45 WX-lora by OK5TVR
20260517051558OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g004t040r000p004P...h98b10103L45 WX-lora by OK5TVR
20260517061602OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_180/00 g004t050r000p004P...h73b10095L90 WX-lora by OK5TVR
20260517064605OK5TVR-5>APRS,qAO,OK1VP-10:!4947.31G/01317.40E_135/002g005t053r000p004P...h68b10093L124 WX-lora by OK5TVR
20260517084610OK5TVR-5>APRS,qAO,OK1VP-10:!494?.38N/01317.40E_315/001g004t058r000p004P...h51b10090L417 WX-lora by OK5TVR
20260517093114OK5TVR-5>APRS,qAS,OK1RPL-15:!85"01317.40E_270/004g012t02v:20>&..h48b10087L431 DR:-121 DS:-21.25