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
20260908064138OK0BPL-5>APRS,qAR,OK4MD-13:!4973D%013r3:O_+dhV1Zznc9onG"Pa
20260908075638OK0BPL-5>APRS,qAR,OK4MD-13:!4940.81Nk413bg+89E_19902g005t071⚙ L<22P000h62b10115 WX by OK5TVR
20260908082638OK0BPL-5>APRS,qAR,OK4MD-13:!4940.5̯01327.89E_180/001g004t075r000L168P000h54b10110 WX by OK5TR
20260908094138OK0BPL-5>APRS,qAR,OK4MD-13:!4940.D/01327.89E_222/002g006t082r000L228P000h42b10090 WX by OK5TVR
20260908104139OK0BPL-5>APRS,qAR,OK4MD-13:!4940.heK/01327.89E_222/008g018t084r80:19P000h34b10083 WX RI0O[5TVR
20260908112639OK0BPL-5>APRS,qAR,OK4MD-13:!4940>x5J/01327.89E_222/007g014t08406PJ421P000h31b10075 WX by OKTR