APRS Packet Errors for OK1VCF-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
20260228005214OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4939.59N/01426.89E_000/(30g000t037b10268h92XPIC 16F628mod+12F675wx
20260228015223OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4939.59.&01426.89E_000/000g000t036b10269h94XPIC 16F628mod+12F675
20260228045231OK1VCF-5>APEWX0,OK0BNJ-2,OE3XWJ-10,OE3SZA-15,OK0BR-1*,qAR,OK1TZL:!4939.59N/01426.89E_000/0
20260228050729OK1VCF-5>APEWX0,OK0BNJ-2,OK0BR-1*,WIDE3-2,qAR,OK0BPT-1:!4939.59N/01ò26.89E_000/000g000t033b10272h95XPIC 16F628mod+12F675wx
20260228060737OK1VCF-5>APEWX0,OK1OQH-2,OE3XWJ-10,OE3SZA-15,OK0BR-1*,qAR,DB0POB:!4939Ö49N/01426.89E_000/000g000t032b10274h96XPIC 16F628mod+12F675wx