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
20260513161002OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK1TZL:!4939.59N/01426.89Ş```^`````P`jlb``phhp@blldpVbdlnj
20260513182509OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK0BPT-1:!4939.59N/01426.89E_000/p0g000t054b10080h54XPIC 16F628mod+12F675wx
20260513191010OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK0BPT-1:!
20260513191010OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK0BPT-1:!
20260513201019OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK0BPT-1:!4939.59N/0136.89E_000/000g000t04b10082h70XPIC 16F628mod+12F675wx
20260513215521OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK1TZL:!493,59N/01426.89E_000/000g000t044b10076h76XPIC 16F628mod+12F675wx