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
20260411133252OK5TVR-5>APRS,qAO,OK1CTR-10:!7:.38N/01317.40E_000/008g018t055r000p
20260411134752OK5TVR-5>APRS,qAS,OK1RPL-15:!4947>38_>11317.40E_045/006g014t056r000p000P...h61b10091L157 WX-lora by OK5TVR DR:-121 DS:-19.75
20260411140254OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/PQUQQ.40E_000/008g016t055r000p000P..jlu=b20
20260411141755OK5TVR-5>APRS,qAR,OK1KUN-2:!4947.38N/@UgB*43|H
20260411144758OK5TVR-5>APRS,qAS,OK1RPL-15:!4947."9O>01317.40E_000/005g008t056r000p000P...h59b10091L96 WX-lora by OK5TFR DR:-121 DS:-20.25
20260411150259OK5TVR-5>APRS,qAO,OK1CTR-10:!4947ǧ0X`?9!3> 18g015xy|83
20260411160304OK5TVR-5>APRS,qAS,OK1RPL-15:!4942.38N/ DR:-121 DS:-20.00
20260411164808OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/09;17.49U`8Onn0)&8
20260411180314OK5TVR-5>APRS,qAO,OK1CTR-10:!69,38N/980E?045/007g009t048r3
20260411180314OK5TVR-5>APRS,qAS,OK1RPL-15:!49473N/01317.40E_045/007g009t048r000p000P...h61b10086L0 WX-lora by OK5TVR DR:-121 DS:-18.75