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
20251221150131OK5TVR-5>APRS,qAS,OK1RPL-15:!494W.f8*U DR:-121 DS:-22.25
20251221153133OK5TVR-5>APRS,qAO,OK1VP-10:!49471G01317.40E_315/007g012t035r000p002P...h100b10107L0 WX-lora by OK5TVR
20251221163136OK5TVR-5>APRS,qAR,OK1KUN-2:!457"38N/01317.40E_222/008g012t034r000p002P...h100b10107L0 WX-lora by OK5TVR
20251221164637OK5TVR-5>APRS,qAR,OK1KUN-2:!4947:΅rq{&3E_300/338g013t034r000p002P...h100b10107L0 WX-lora by OK5TVR
20251221181640OK5TVR-5>APRS,qAR,OK1KUN-2:!4947?&01317N45si615/007g010t034r000p002P...h100b10097L0 m,+re$fyN[4ŗ
20251221190141OK5TVR-5>APRS,qAO,OK1VP-10:!4947N38NI61317.40E_315/007g016t034r000p002P...h100b10108L0 WX-lora by OK5TVR
20251221193142OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/=1=$73u_PVP,V10g016t033r000p002P...h100b10098L: WX-lo"apgy OK5TVR
20251221201644OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.1N/01317.40E_000/008g011t034r000p002P...h100b10108L0 WX-lora by OK5TVR
20251221201644OK5TVR-5>APRS,qAO,OK1VP-10:!4947.38N/01317.40E_000/00XgPW1t034r000p002P...h100b10108L0 WX-lora byOK9TVW
20251221201645OK5TVR-5>APRS,qAS,OK1RPL-15:!<5FRC 0a.d0Z000/008g011t034r000p002P...h100b10108L0 wxnmpa by OK5TVR DR:-121 DS:-21.50