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
20260917204223OK0BPL-5>AZRY,qAO,OK1CTR-10:!414°.85N/01327.89E_180/001g004t060r000L000P000h57b10108 WX by OK5TVR
20260917215722OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/01327.^9E_315/001g003t058r000L000P000h63b10109 WX by OK5TVR
20260918004222OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/01327.49E_180/
20260918005722OK0BPL-5>APRS,qAR,OK4MD-13:!0=0t.85N/01327.mlE_135/003g005t056r000L00r220h74b10107 WX by%K5TVR
20260918014222OK0BPL-5>APRS,qAR,OK4MD-13:!4940.85N/01327.89%?180/003g006t055r000L000P000h72b10108 WX by OK5TVR