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
20260218023028OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.58./1=N40%_180/005g010t034r000p0027P...h94b10056L0 WX-lora by OK5TVR
20260218061539OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/01317.40E_180/00 g00 t033r000p0027P...h91b10056L0 rUVNGY
20260218061540OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_180/00 g00 t033r000p0027P...h91b10056L0 WX-lora by OK5TVR
20260218071544OK5TVR-5>APRS,qAO,OK1VP-10:!83Q$38N/01317.40E_180/00W004t033r000p0027P...h92b10067L13 WX-lora by OK5TVR
20260218071544OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317E_180/002g004t033r000p0027P...h92b0067L13 WX-lora by OK5TVR
20260218080045OK5TVR-5>APRS,qAR,OK1KUN-2:!402.38N/01317.40E_222/001g002t034r000p0027P...h89b10066L26 WX-lora by OK5TVR
20260218081547OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/0131>.40E_180/04ﰰ0t035r000p0027P.".a86b100eEU +;kx OK5TVR