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
20261101215755OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/01327.89…“045/000g003t040r000L000P003h89b10275 WX by OK5TVR
20261101215755OK0BPL-5>APRS,qAO,OK1CTR-10:!4940®0•D/01327.89E_045/000g003t040r000L000P003h89b10275 WX by OK5TVR
20261101221255OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85Ž#<1327.89E_315/000g002t040r000L000P003h90b10276 WX by OK5TVR
20261101222755OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/ð=3þ7.89E_000/001g005t040r000L000P003h90b10275 WX by OK5TVR
20261101232755OK0BPL-5>APRS,qAO,OK1CTR-10:!4940.X5H/01327.89E_270/000g004t040r000L000P000h91b10271 WX by OK5TVR