APRS Packet Errors for OK1VCF-6 (last 168 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
20261027041316OK1VCF-6>APEWX0,OK0MIL-1,OK0BR-1*,WIDE2-1,qAR,OK0BPT-1:!5041.57N/0=532.37E_000/000g000t035b10236h93XPIC E2435B3F6051668587888184847A727E7E65
20261027042821OK1VCF-6>APEWX0,OK0MIL-1,OK0BR-1*,WIDE2-1,qAR,OE5XIM-10:!504).57N/01532.37E_000/000g000t034b10237h93XPIC E2435B3F6051648587;88184847A727D7E64
20261027051329OK1VCF-6>APEWX0,OK0MIL-1,OK0BR-1*,WIDE2-1,qAR,OE5XIM-10:!5041.57N/01532.37E_000/0P0g000t035b10238h92XPIC E2445B3F6051658487888184847A727D7E65
20261028214731OK1VCF-6>APEWX0,OK0MIL-1,OK0BR-1*,WIDE2-1,qAR,OK1RPL-1:!5041.51N/01532.+7E_000/000g000t348b10264h89XPIC E235A3F60507E8386877F82827C7C7E7C7E