APRS Packet Errors for OK1RPL-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
20250411172926OK1RPL-5>APRS,qAS,OK1JRA-16:!4943.28N/01309.04E_180/00 g00 t058r000p000P...h47b10141L0 WX-lora by OK5TVR DS 8.00 RS -72
20250411174618OK1RPL-5>APRS,qAS,OK1JRA-16:!4943.28N/01309.04E_222/00 g00 t057r000p000P...h51b10142L0 WX-lora by OK5TVR DS 10.50 RS -75
20250411192737OK1RPL-5>APRS,qAS,OK1JRA-16:!4943.28N/01309.04E_270/00 g00 t051r000p000P...h88b10157L0 WX-lora by OK5TVR DS 10.00 RS -74
20250411194428OK1RPL-5>APRS,qAS,OK1JRA-16:!4943.28N/01309.04E_270/00 g00 t049r000p000P...h100b10159L0 WX-lora by OK5TVR DS 12.75 RS -76
20250411200121OK1RPL-5>APRS,qAS,OK1JRA-16:!4943.28N/01309.04E_270/00 g00 t048r000p000P...h100b10160L0 WX-lora by OK5TVR DS 9.25 RS -77