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
20260327181132OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK0BPT-1:!4939.59N/01426.89E_000/00°f000t037b10253h60XPiD 16F628mod+12F675wx
20260327181139OK1VCF-5>APEWX0,OK0BR-1,OK0BAD-2,OK0DJ-1,DB0SPN,WIDE3,qAS,DF1XC-7:!4939.59N/01426.89E_000/00°f000t037b10253h60XPiD 16F628mod+12F675wxÛ
20260327181206OK1VCF-5>APEWX0,OK0BR-1,OK0BAD-2,OK0DJ-1,SR3NJE*,qAR,SQ3XZ-2:!4939.59N/01426.89E_000/00°f000t037b10253h60XPiD 16F628mod+12F675wx
20260327181306OK1VCF-5>APEWX0,OK0BR-1,OK0BAD-2,OK0DJ-1,OK1OBR-1,WIDE3*,qAR,OK0DBF-1:!4939.59N/01426.89E_000/00°f000t037b10253h60XPiD 16F628mod+12F675wx
20260327184134OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK1TZL:!4939.59N/‹1426.89E_000/000g000t036b10256h65XPIC 16F628mod+12F675wx
20260327192636OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK1TZL:!4939.59N/P1426.15E_000/000g000t032b10259h70XPIC 16F628mod+12F675wx
20260327221145OK1VCF-5>APEWX0,OK0BR-1*,WIDE3-3,qAR,OK0BPT-1:!4939.59N/01426.89E_000/0Ô0g000t028b10268h79XPIC 16F628mod+12F675wx