Quick answer: Rust admin commands start with ownerid "Name" "owner" in the server console or over RCON to become owner instantly, with no reconnect needed, then run server.writecfg so it survives a restart. Kick with kick "Name" "reason" , ban with ban "Name" "reason" or banid for a SteamID that cannot be dodged by a name change, and undo it with unban .
Everything below applies to PC dedicated servers for Rust. Rust Console Edition on PS5 and Xbox runs a separate, more limited admin system with no F1 developer console.
The three places you can type a command
Admin work happens in one of three interfaces, and knowing which one you are in prevents most confusion.
- Server console: the RustDedicated.exe window on your host machine, or the console tab in your hosting panel.
- RCON / WebRCON: a remote connection on your RCON port (default
28016), used by tools such as RustAdmin or WebRCON. - In-game F1 console: press F1 in game. Admin commands only work here once your account is authed as owner or moderator.
Commands are not case-sensitive. Some take a value (fps.limit 144), others are toggles (noclip).

Make yourself owner or moderator
Granting yourself admin takes one line. Run it in the server console or over RCON:
- Type
ownerid <SteamID64> "Name" "owner"for full admin (auth level 2), ormoderatorid <SteamID64> "Name"for the lower moderator tier (auth level 1). - Run
server.writecfgimmediately afterwards. - Check
users.cfg, where auth levels and permissions are stored alongside the ownerid and moderatorid entries.
The assignment is effective at once, so you do not need to reconnect (Crucible Docs); some guides, such as LordHosting, still advise reconnecting. Skip step 2 and the assignment can be lost on the next restart. To revoke access later, use removeowner <SteamID64>.
Kick, ban and unban without locking yourself out
Moderation is the core of daily admin work on any hosting server for Rust. These are the commands you will reach for most:
| Command | What it does |
|---|---|
kick "name" "reason" |
Disconnects a player |
kickall |
Kicks every connected player |
ban "name" "reason" |
Bans by name |
banid <SteamID> |
Bans by Steam ID - safer against name changes and duplicate names |
unban <SteamID> |
Removes a ban |
banlist |
Lists banned players |
banlistex |
Shows bans with reasons and names |
mutevoice <SteamID> / unmutevoice |
Silence or restore voice chat |
mutechat <SteamID> / unmutechat |
Disable or restore text chat |
A duration suffix such as ban "Name" "cheating" 7d is the documented way to make a ban temporary. Confirm the result in banlistex rather than assuming it took, and prefer banid with an explicit SteamID for repeat offenders.
Teleport, spectate and move people around
Teleport commands make support calls quick when a player is stuck or reporting a cheater.
teleport "name"sends you to a player.teleport "name1" "name2"sends one player to another.teleport2me "name"brings a player to you.teleportpos "x y z"sends you to coordinates.spectatewatches players, anddebugcameragives you a free camera for reviewing a scene.
Give items, spawn entities and run events
Spawning commands are useful for events, compensation and testing builds:
| Command | What it does |
|---|---|
inventory.give <item> <amount> |
Give yourself an item (use short names, e.g. wood) |
inventory.giveto "name" <item> <amt> |
Give an item to a specific player |
inventory.giveall <item> <amt> |
Give an item to every player |
inventory.givebp <item> |
Give a blueprint |
spawn <entity> |
Spawn an entity or NPC |
noclip flies through everything and god true enables god mode. These are admin tools that function like cheats when misused, so keep them off public accounts and never leave an authed session unattended.
Time of day and entity inspection
env.time 12 sets the time of day, with 12 as noon. When you need to identify what something on the map actually is, ent who inspects entities (per GameServerHosting.co.uk's command list).
Save, restart and keep your settings from vanishing
Settings typed into the console do not always stick. This is where most new owners lose their admin rights:
| Command | What it does |
|---|---|
save / server.save |
Force an immediate world save |
server.writecfg |
Write current settings to config files |
server.readcfg |
Reload configuration |
server.backup |
Back up the server folder |
restart <seconds> |
Restart with a countdown warning |
quit |
Saves and shuts the server down |
server.writecfg is what persists owner and moderator lists and server variables across restarts. Keep server.cfg in the location your host documents (PlayYourWay covers where server.cfg goes and which Startup fields it overrides).
Check who's on and how the server is doing
Quick status checks answer most "is the server down" questions before players ask them:
| Command | What it does |
|---|---|
status |
Connected players, ping and Steam IDs |
players / playerlist |
Print currently connected clients |
users |
User info for players on the server |
serverinfo |
Uptime, FPS, players, memory |
server.fps |
Current server framerate |
say "message" |
Message to the whole server |
status is the one to run first when someone reports a problem: it gives you names, pings and Steam IDs in a single readout you can act on.
Player commands that don't need admin
None of these require an auth level, so they work on any server:
killrespawns you when stuck.perf 1shows FPS,perf 2adds memory,perf 0hides it.fps.limit 144caps your frame rate.graphics.fov 90sets field of view.client.connect IP:PORTjoins a server directly.combatlogshows your recent damage dealt and taken.bind [key] [command]binds a command to a key.quitcloses the game.
What Rust Console Edition players can't do
PlayStation and Xbox servers use a different, more limited admin system with no F1 developer console. The PC syntax in this guide does not apply there, and console servers are managed through separate, more limited tools (see Helios RCE's Rust Console bot documentation). If you play on console, treat PC admin guides as a different game's documentation.
Common mistakes that cost you a server
- Assuming a ban duration will apply as typed without checking
banlistexafterwards. - Banning by name only, which fails against duplicate names and name changes.
- Expecting console-typed server variables to persist without writing the config.
- Treating any third-party command list as gospel. Many are copied from each other and carry errors, and Facepunch's own wiki covers server creation rather than a complete command reference.
Verify syntax in a live console, especially after monthly updates. The October 2026 "Printed and Polished" patch, with its Blueprint Rework and the Uzi 9mm, is a reminder that command behaviour can shift between patches.
Admin work is only half of running a server
Admin commands solve the immediate problems: a cheater, a stuck player, a settings file that forgot your name. Keeping a server populated is a different discipline, and the tools you reach for between incidents matter as much as the ones you reach for during them.
Sources
- Facepunch Rust Wiki: Creating a server
- Facepunch: Printed and Polished update notes
- XGamingServer: Rust Admin Commands & Console Commands
- LordHosting: Rust Console Commands: Full Admin & Player List
- Crucible Grounds: How to become admin, Kick and ban players
- OuiHeberg: Rust admin commands
- MatrixHost: Rust server admin commands
- VGKami: Rust server admin commands
- GameServerHosting.co.uk: Rust admin console commands
- GameServerKings: Rust console commands, admin commands
- Spot.gg: Rust admin commands, Rust console commands
- Dustbowl Games: Rust admin commands and permissions
- PlayYourWay: Rust server.cfg and admin commands
- Helios RCE: Admin commands documentation







Comments
Join the Conversation
Share your thoughts, ask questions, and connect with other community members.
No comments yet
Be the first to share your thoughts!