APRS Packet Errors for OK1VCF-5 (last 24 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
20260429185243OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4939.59N/0142.89E_000/000g000t0
20260429235319OK1VCF-5>APEWX0,OK0BNJ-2,OK0DJ-1,SR3NJE*,qAR,SP3TLU:!4939.59N/01426.89E_000/0
20260430002306OK1VCF-5>APEWX0,OK0BNJ-2,OK0BR-1*,WIDE3-2,qAR,OK0BPT-1:!4939..9N/01426.89E_000/000g000t029b10360h71XPIC 16F628mod+12F675wx
20260430010802OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK2JIB-1:!4939.59N/01426.89E_000/P00
20260430011242OK1VCF-5>APEWX0,OK0BR-1,OK0BBK-2,OK1OBR-1*,WIDE3-1,qAR,OK2JIB-1:!4939.59N/01426.89E_000/P00
20260430013804OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4939.59N/01426.89```^```````dpb`fl`nh@blldpVbdlnZ
20260430023829OK1VCF-5>APEWX0,OK0BAD-2,OK0DJ-1,SR3NJE*,qAR,SP3TLU:!4939.59N/01426.89E_0
20260430030808OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4 39.59N/01426.89E_000/000g000t026b10364h78XPIC 16F62
20260430032312OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK2JIB-1:!4939.59N/01426./3:,!#7#;<
20260430043815OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4939.59N/014T.89E_000/000g000t027b10372h78XPIC 16F628mod+12F675wx
20260430073823OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OE5XIM-10:!4939.59N/0146.89E_000/000g000t052b10366h34X0IC 16F628mod+12F675wx