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
20260222071552OK5TVR-5>APRS,qAO,OK1CTR-10:!4947>2)_>01317.40E_180/002g005t045800ppb;
20260222073051OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/>hYS3v={_4 201X.&.h100b10131L8 WX-lora by OK5TVR
20260222081553OK5TVR-5>APRS,qAO,OK1VP-10:!4947.s8J+01317.40E_135/005g014t045r001p001P...h100b10130L17 WX-lora by OK5TVR
20260222090058OK5TVR-5>APRS,qAO,OK1VP-10:!4947.M/61317.40E_222/005g012t046r000p002P...h100b10130L24 WX-lora by OK5TVR
20260222094604OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/013178S<90/00T026t047r000p002P...h99b10129L27 WX-lora byEk5
20260222113108OK5TVR-5>APRS,qAO,OK1CTR-10:!4947B#;3=$40E_1)!/!15g012t048r000p002P.,h;:`10129L51 W8-lora by OK5TR