1. Know what Rust already does for you
Every official Rust server runs Easy Anti-Cheat (EAC). When EAC catches someone, Facepunch bans them from every server — you don't have to do anything. EAC catches known cheats; it misses newer or private ones, and it can't judge behaviour.
Rust also has a server-side antihack system that watches movement and actions. When a player flies, moves impossibly fast or hits through things they shouldn't, it records a violation (flyhack, speedhack, noclip and similar) and can kick them. It's most useful as a pattern: one violation can be lag, the same player triggering it again and again is a lead.
Players can report each other with F7. A single report means little — losing players report winners all the time — but several reports from *different* players about the same person is worth a look.
2. The signs that actually mean something
- Headshot rate far above the norm — per weapon. A good player might land a lot of headshots with a bolt rifle; landing 60–70% headshots with an automatic rifle over many kills is not normal. Always compare against the same weapon, and against *your own server's* average rather than a number from the internet.
- Long-range kills that keep happening. One 300 m kill is a highlight. A string of them, mostly headshots, in a short session is a pattern.
- Kills per hour that don't fit. Compare kills against hours actually played this wipe. Someone with 2 hours played and 40 PvP kills deserves a second look.
- Knowing where people are. Players who walk straight to hidden bases, pre-aim doorways or track people through walls (ESP) usually show it in *where* they go, not only in their stats.
- Repeated antihack violations and F7 reports from many players at the same time as the above.
3. Gather evidence before you act
- Write down what was reported — who, when, where (grid), and what happened.
- Look at the fight from both sides: the victim's death (weapon, distance, headshot) and the suspect's kills around that time.
- Watch them. As an admin you can spectate a player in-game. Watch how they track targets, whether they look at walls with people behind them, and how they move.
- Check history: earlier warnings, previous reports, alt accounts on the same team.
- Save it — screenshots, clips and your notes — somewhere that doesn't expire. A ban appeal six weeks later is much easier when you can show why.
4. Ban fairly
Once you're confident, ban with a clear reason using the console: banid <steamid> "name" "reason" (or your moderation plugin's command). Keep the reason short and specific — “aimbot: 71% HS rate with AR over 40 kills, 4 F7 reports” — because that's what you'll be judged on if they appeal. Tell the people who reported it that it's been handled; it's the best way to keep honest players reporting.
How PlayerAnalytics does this for you
Questions
Can server admins see Easy Anti-Cheat detections?
No. EAC bans are handled by Facepunch across all servers. What you can see on your own server is Rust's antihack violations, F7 reports and the players' own stats.
What headshot rate means someone is cheating in Rust?
There's no single number — it depends on the weapon and your server. Compare each player with your own server's average for the same weapon over a decent number of kills, and look for other signals at the same time.
Should I ban on F7 reports alone?
No. Reports point you at who to watch; the ban should rest on evidence you've checked yourself.
Your server, without the guesswork.
Everything in this guide — tracked, flagged and handled for you by PlayerAnalytics.