APRS Packet Errors for OK0BPL-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
20260907022638OK0BPL-5>APRS,qAR,OK4MD-13:!05p*85N/01327.89E_090/003g007t056r000L000P00h9b1021) ky OK5TVR
20260907031138OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/07341(8E_180/002g005t056r000L000P00HVb10211 WX by EA?TVR
20260907042639OK0BPL-5>APRS,qAO,OK1CTR-10:!4940.85N/3;9uo135/002g005t055r000L0!%
20260907045638OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/0;.89E_222/001g004t056r0205P0vL<3 WX b9`NJhY
20260907054138OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/01327.; Eo270/001g003t056r000L016P00h6b10212 WX by OK5TVR
20260907055638OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/112?.89E_222/001g003t056r000L "0@0a5=3dg10213 WX by OK5TVR