APRS Packet Errors for KC6OYN (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
20250913055233KC6OYN>APOTW1,WA6ZSN,WIDE1*,qAR,N6DGM-10:!3429.67Nl¦†Š@õð!3429.67N/11942.76W_218/002g003t059P000h75b10251OTW1
20250913065644KC6OYN>APOTW1,KF6ILA-10*,qAR,W6ZU-10:!3429(67N)11942.76W_324/006g007t059P000h75b10247OTW1
20250913083314KC6OYN>APOTW1,WA6ZSN,WIDE1*,qAR,N6DGM-10:!3429.67Ntelleza@gmail.com www.crebc.org
20250913100941KC6OYN>APOTW1,WA6ZSN,WIDE1*,qAR,N6DGM-10:!3429.67N/11942.7‚l´¦œà®’ˆŠd@áðT#274,124,147,255,045,019,10111011
20250913103353KC6OYN>APOTW1,WA6ZSN,WIDE1*,qAR,N6DGM-10:!3429.67N/11942.76W_326/0
20250913112204KC6OYN>APOTW1,WA6ZSN,WIDE1*,qAR,N6DGM-10:!3429.67N/11942.76W_000/0