RustRust Server Console Commands (Admin Cheat Sheet, 2026)
The Rust server console commands admins actually use: kick, ban, ownerid, teleport, save, restart, entity cleanup and performance checks, grouped.
Updated Oct 1, 2026 · 7 min read
On this page
- Where do you type Rust server commands?
- Player and moderation commands
- Admin and permission commands
- Teleport and in game admin tools
- World, time and event commands
- Entity cleanup commands
- Performance and server info commands
- Config commands
- Oxide and Carbon commands
- The easy way: buttons for the common ones
- FAQ
The Rust server console commands you will use most are status to list players, kick, ban and banid to remove them, ownerid plus server.writecfg to make admins, server.save before anything risky, and restart to reboot with a countdown. Type them in the server console (or RCON) without a slash. Below is every command worth knowing, grouped by job, with the exact syntax.
Where do you type Rust server commands?
There are two places, and they behave a little differently:
- The server console. On a self hosted box that is the RustDedicated window or an RCON tool. On GamezServers it is the Console tab in the panel. Commands run as the server, so you never need to be admin and you never type a
/. - Your in game F1 console. Works for the same admin commands once you are an owner or moderator, plus the client side admin tools like
noclipanddebugcamerathat only make sense when you are in the world.
Chat commands that start with / (like /tp or /kit) come from Oxide or Carbon plugins, not from Rust itself. They are a different system.
One habit worth building: after any change to admins or bans, run server.writecfg. Without it, those changes live in memory and vanish on the next restart.
Player and moderation commands
| Command | What it does |
|---|---|
status |
Lists connected players with SteamID64, ping and connection time |
players |
Shorter player list |
playerlist |
Player list in a format tools can read |
users |
User info for everyone on the server |
sleepingusers |
Lists sleepers (players who are offline but still in the world) |
kick "Name" "reason" |
Kicks a player. The reason shows in chat |
kickall "reason" |
Kicks everyone, handy right before a restart |
ban "Name" "reason" |
Bans an online player by name |
banid 76561198000000000 "Name" "reason" |
Bans by SteamID64, works for offline players |
unban 76561198000000000 |
Removes a ban |
banlist / banlistex |
Lists bans. banlistex includes names and reasons |
mute "Name" / unmute "Name" |
Blocks or restores a player's chat |
server.writecfg |
Saves admins and bans to disk so they survive restarts |
Names with spaces need quotes. When two players have similar names, use the SteamID64 from status instead, so you do not ban the wrong person.
Admin and permission commands
| Command | What it does |
|---|---|
ownerid 76561198000000000 "Name" |
Makes someone an owner (full admin) |
moderatorid 76561198000000000 "Name" |
Makes someone a moderator |
removeowner 76561198000000000 |
Removes owner status |
removemoderator 76561198000000000 |
Removes moderator status |
server.writecfg |
Writes the change to cfg/users.cfg |
The full flow for adding an admin:
ownerid 76561198000000000 "YourName"
server.writecfg
Then the player reconnects. Our admin guide covers finding your SteamID64 and the owner vs moderator difference.
Teleport and in game admin tools
These run from your F1 console once you are an admin:
| Command | What it does |
|---|---|
noclip |
Fly through walls. Run again to stop |
debugcamera |
Detached free camera for checking bases |
god true / god false |
Toggles taking damage |
teleport "Name" |
Teleports you to a player |
teleport "Name1" "Name2" |
Moves player 1 to player 2 |
teleport2me "Name" |
Brings a player to you |
teleportpos 1000 50 -500 |
Teleports you to X Y Z coordinates |
teleportlos |
Teleports you to where you are looking |
server.printpos |
Prints your current position |
spectate "Name" |
Spectates a player |
inventory.give rifle.ak 1 |
Gives you an item by short name |
inventory.giveall wood 1000 |
Gives an item to everyone online |
Our take: on a friend server, agree on rules for these up front. Admin teleports and item spawns are the fastest way to kill a wipe for everyone else.
World, time and event commands
| Command | What it does |
|---|---|
env.time 12 |
Sets the time of day (0 to 24) |
env.addtime 6 |
Skips forward a number of hours |
say "Message" |
Sends a server message to chat |
heli.calltome |
Sends the patrol helicopter to your position |
entity.spawn minicopter.entity |
Spawns an entity by prefab name where you are |
server.save |
Forces a world save right now |
restart 300 "Restarting for an update" |
Restarts after 300 seconds and warns players |
quit |
Shuts the server down cleanly |
Always run server.save before quit or before stopping the server from a panel. Anything built since the last autosave is lost otherwise.
Entity cleanup commands
Big or abandoned bases are the usual cause of a laggy late wipe. These help:
| Command | What it does |
|---|---|
entity.countby 76561198000000000 |
Counts entities placed by a player |
entity.deleteby 76561198000000000 |
Deletes everything a player has placed |
entity.find_entity cupboard |
Lists entities whose prefab name matches |
entity.find_radius 20 |
Lists entities near you |
entity.deleteby is permanent and has no undo. Take a backup first, and use it on cheaters or players who left a base the size of a monument behind.
Performance and server info commands
| Command | What it does |
|---|---|
server.fps |
Prints the current server frame rate |
serverinfo |
Players, queue, entity count, uptime, framerate and memory in one line |
version |
Prints the Rust build the server runs |
server.netprotocol |
Prints the network protocol clients must match |
pool.print_memory |
Shows object pool usage |
serverinfo is the one to remember. Its entity count and framerate tell you more about lag than anything players say in chat. Our Rust lag and low FPS fix explains what healthy numbers look like and what to do when they drop.
Config commands
| Command | What it does |
|---|---|
server.writecfg |
Writes admins, bans and saved settings to the cfg folder |
server.readcfg |
Re-reads serverauto.cfg and server.cfg without a restart |
Typing a convar name on its own, like decay.scale, prints its current value. Typing it with a value sets it until the next restart. To make it stick, put it in server.cfg. The settings themselves are covered in Rust server.cfg settings explained.
Oxide and Carbon commands
If you run a plugin framework, these manage it from the same console:
| Oxide | Carbon | What it does |
|---|---|---|
oxide.plugins |
c.plugins |
Lists loaded plugins |
oxide.reload Name |
c.reload Name |
Reloads one plugin after a config edit |
oxide.reload * |
c.reload * |
Reloads every plugin |
oxide.grant user Name perm |
c.grant user Name perm |
Gives a plugin permission |
Setup and permissions are in how to install Rust plugins.
The easy way: buttons for the common ones
On a GamezServers Rust server the most used commands are buttons in the panel: Save world, Broadcast, Player list, Kick player, Ban by Steam ID, Unban, Make admin, Save admins and bans, Set time of day, and Reload Oxide plugins or Reload Carbon plugins. They fill in the syntax for you, and the full console sits right next to them for everything else. The Players tab shows who is online with kick and ban next to each name.
FAQ
Do Rust console commands need a slash?
No. Console commands like kick or server.save are typed without a slash. Commands that start with / are chat commands added by Oxide or Carbon plugins.
Why did my admin or ban disappear after a restart?
You did not run server.writecfg after the change. Rust keeps admins and bans in memory until that command writes them to users.cfg and bans.cfg.
How do I find a player's SteamID64 on my server?
Run status in the console. Every connected player is listed with their 17 digit SteamID64, which you can paste into banid, ownerid or entity.deleteby.
How do I restart a Rust server with a warning?
Run restart followed by a number of seconds and a message, for example restart 300 "Restart in 5 minutes". Players get the countdown in chat. Run server.save first if you want to be sure nothing is lost.
How do I check a setting's current value?
Type the convar name on its own in the console, for example server.maxplayers or decay.scale. Rust prints the current value. Add a value after it to change it until the next restart.
Skip the setup. Your own Rust server.
Then $19.99/mo. Just trying it? $5.00 for 3 days