Rust Admin Commands: The Complete List & How to Use Them

Admin commands let you moderate players, teleport, spawn items, run events, control the weather, and manage your Rust server in real time. This guide covers how to grant yourself admin, where to type commands, and every command worth knowing.

This guide covers Rust on PC

Rust Console Edition (PlayStation / Xbox) uses a different, more limited admin system with no F1 developer console. See the Console Edition section near the end.

1. How Admin Permission Works

Rust has three auth levels. Any level above 0 counts as admin, and the server lets both level 1 and level 2 run the admin commands on this page, including noclip, god, spawn and give. The differences are small: only a level-2 owner can run ownerid from in-game, and only level 2 sees player IP addresses in status and players.

That means moderatorid is not a "safe" trial-staff rank: a moderator can spawn items and fly just like you. Our moderation playbook explains why item spawning and noclip are the two permissions that do the most damage in the wrong hands. For staff who should only kick, ban and mute, leave them at level 0 and give them just those powers through a plugin permission group; Rust Oxide permissions 101 shows how.

Rust has two kinds of console input: commands you run once (like kick) and convars (variables) that hold a setting (like decay.scale). Most player commands live under the global. namespace — e.g. global.kick — but you can type the shorthand (kick) and it works the same. This guide uses the shorthand throughout.

2. Make Yourself Admin

Run these from your server console or RCON. You cannot grant yourself admin from in-game until you already have it.

Step 1: find your SteamID64. It is the 17-digit number starting 7656. Join the server, then run users in the server console: it prints every connected player as SteamID64 : "name". You can also paste your Steam profile URL into steamid.io.

Step 2: grant yourself owner.

ownerid 76561197960287930 "YourName" "owner"

The server replies Added owner YourName, steamid 76561197960287930. The two quoted values are a display name and a note; they are optional, but they make users.cfg readable later.

Step 3: reconnect if commands are refused. The server applies the new auth level to a player who is already online, but Facepunch's guide still says to reconnect, and that fixes nearly every "I ran ownerid and nothing works" report. After rejoining, the console or log shows your connection with has auth level.

You do not need server.writecfg for admins

ownerid, moderatorid, removeowner and removemoderator each save users.cfg the moment you run them, so admin status already survives a restart. Facepunch's own server guide puts it plainly: "No need to save the changes after doing this, it is done automatically now." server.writecfg does something else: it writes the server's saved settings to serverauto.cfg (and re-saves users.cfg along the way).

Setting it from the panel

ownerid can be set directly from the Console tab of your Rust game server host. Run the command above, then reconnect. Your admin status persists across restarts on its own.

Where users.cfg lives on a GSK server

GSK's Rust servers start with the server identity myserver, so admins are stored in:

server/myserver/cfg/users.cfg

Open it from the panel's Files tab. Each admin is one line, in exactly the format the commands above write:

ownerid 76561197960287930 "YourName" "owner"
moderatorid 76561198000000000 "StaffName" "trusted staff"

Edit this file only while the server is stopped. The running server keeps its own copy of the admin list in memory and rewrites users.cfg from it whenever an admin changes, so hand edits made while it runs get overwritten. Bans are kept separately in bans.cfg in the same folder.

The same folder is where your own server.cfg goes. The server reads serverauto.cfg first and server.cfg second, so anything you set in server.cfg wins over what server.writecfg saved.

3. Where to Type Commands

Vanilla commands are typed without a leading slash. Commands that start with / are almost always from a plugin.

The same F1 console also carries a set of client-side commands any player can run - FPS caps, field of view, keybinds and the combat log. Those need no admin rights and change only your own game; they are covered in Rust Console Commands.

4. Player & Admin Management

5. Moderation & Muting

6. Movement, Camera & Player State

7. Spawning Items & Entities

Item commands live under the inventory. namespace (shorthand in brackets):

Item short names are values like rifle.ak, wood, stones, metal.fragments, scrap, lowgradefuel. For example:

inventory.give rifle.ak 1
inventory.giveall scrap 500

8. Entity Tools

These act on whatever entity you are looking at — aim your crosshair at it first. Useful for cleaning up griefed builds or checking ownership.

del is not reversible

del removes every instance of a prefab across the whole map. Double-check the prefab name before running it, and take a backup first.

9. Events

10. Time & Weather

admintime only changes your screen

env.time changes the time for everyone on the server; admintime only changes it for you — handy for screenshots without disrupting players. Reset with admintime -1.

11. Server Management

12. Info & Debugging

13. Keybinds

Bind any command to a key so you can toggle it instantly. Binds are client-side — save them with writecfg (not server.writecfg).

bind p noclip
bind b "god true"
writecfg

Syntax is bind <key> "<command>". Use quotes around commands that contain spaces.

14. Finding Commands & Item Names

Two things you will always need: the name of a command, and the exact short name of an item or the prefab path of an entity.

• Find a command: type find <keyword> in the console — e.g. find weather lists every weather command and convar.
• Item short names (for give / spawnitem) and prefab paths (for spawn / del) are documented in the official Facepunch wiki.

This list is curated, not exhaustive

Rust has hundreds of convars beyond the admin commands above. These are the ones you will actually use day to day. For the complete reference, see the official Facepunch console commands wiki.

15. Vanilla vs. Plugin Commands

Many "admin commands" people search for are not vanilla — they come from the Oxide/uMod or Carbon modding frameworks. If your server runs mods, you likely also have chat commands (typed with /) such as:

• Vanish — /vanish (go invisible)
• NTeleportation — /tpr, /home, /tp
• RemoverTool — /remove to delete structures
• Admin Radar — /radar to see players and entities through walls

Everything in the tables above works on any vanilla server once you have admin (auth level 1 or 2). Commands starting with / only exist if the matching plugin is installed — see How to install Oxide for Rust and Popular Rust Plugins.

16. Rust Console Edition

Rust Console Edition (PS4/PS5, Xbox) is a separate product and does not have the F1 developer console. Admin on community servers is handled through an in-game admin menu with a reduced command set — you cannot spawn arbitrary entities or use most convars. If you are on console, use your server host's admin panel rather than this command list.

17. FAQ

How do I make myself admin in Rust?

Run ownerid <SteamID64> "Name" "owner" from the server console or RCON, then reconnect to the server. Rust saves the change to users.cfg (on GSK: server/myserver/cfg/users.cfg) automatically, so server.writecfg is not needed.

How do I open the admin console?

Press F1 in-game. You must already have auth level 1 or 2 for admin commands to work.

How do I fly in Rust?

Type noclip in the F1 console (requires admin, auth level 1 or 2). Type it again to turn it off.

What is the difference between ownerid and moderatorid?

ownerid gives auth level 2 and moderatorid gives level 1. Both can use every admin command on this page, including spawning and noclip. Only a level-2 owner can grant ownerid from in-game and see player IP addresses in status.

How do I enable god mode?

Type god true in the F1 console; god false to disable it.

How do I give myself items?

inventory.give "item" amount (shorthand give), e.g. give rifle.ak 1. Use giveall for everyone or giveto "player" for one player.

How do I use the debug camera?

Type debugcamera in the F1 console to enter free-fly camera mode; run it again to exit. Use debugcamera_unfreeze to move your character independently.

How do I call an airdrop or helicopter?

airdrop.drop triggers an airdrop; heli.calltome sends the patrol helicopter to your position.

How do I mute a player?

admin.mutevoice "name" mutes voice; admin.mutechat "name" mutes text chat. Unmute with the matching admin.unmute... command.

Why is my command not working?

The usual causes are: you are not admin (auth level 1 or 2), you have not reconnected since being granted admin, a typo in the item or player name, or it is a plugin command and the plugin is not installed.

18. What to Read Next

• Getting started with your Rust server
• How to use external Rust Rcon tools
• Rust Oxide permissions 101
• Rust Console Commands - the client-side F1 commands any player can use
• Rust Packet Flooding (Player Tick) Kicks - why players get kicked for packet flooding, and the server limit to raise
• Rust Wipe Guide
• How to Host a Rust Server - the SteamCMD route, ports and hardware if you want to run one yourself

Made with 💜 by GameServerKings