Rust servers are run from the console: kicking and banning players, teleporting, setting time and weather, handing out items, or saving and restarting cleanly. This reference collects the commands that matter, with their syntax – and makes clear which ones work over RCON and which only work in-game.
If you still need to set the server up, installation, server.cfg and port forwarding are covered in how to create a Rust server.
Last checked in August 2026 against Facepunch's official server documentation.
What you will learn
- where commands are entered – F1 console, server console or RCON
- what the namespaces like
server.,env.andweather.mean - which auth levels exist and how to add owners and moderators
- which commands cover moderation, teleporting, environment and items
- how to grant plugin permissions under Oxide/uMod
Contents
- Where commands are entered
- Understanding namespaces
- Auth levels and adding admins
- Moderating players
- Finding players and pulling information
- Teleport and movement
- Managing the server
- Environment: time and weather
- Items, entities and events
- Oxide/uMod: plugin permissions
- Troubleshooting
- Frequently asked questions
- Related articles
Where commands are entered
There are three routes, and they are not equivalent:
| Route | How | Note |
|---|---|---|
| F1 console | press F1 in-game | you must be authed as owner or moderator |
| Server console | directly on the machine | full rights, but no player context |
| RCON / WebRCON | remote over the RCON port (28016 by default) | the usual route on Linux and for admin tools |
noclip above all – only works in the F1 console, never over RCON. Moderation commands such as kick or ban work on all three.Setting RCON up – port, password and firewall – is described in how to create a Rust server.
Understanding namespaces
Rust commands are grouped into namespaces. The prefix tells you what a command acts on:
| Prefix | Governs |
|---|---|
global. | general server commands such as kick, ban and chat |
server. | server configuration: name, player count, world size, save interval |
env. | time of day |
weather. | weather |
inventory. | handing items to players |
entity. | spawning objects in the world |
admin. | administrative extras |
antihack. | anti-cheat protection |
Many global. commands also work without the prefix – kick and global.kick do the same thing. The tables below use the short form.
Auth levels and adding admins
Rust has three levels:
| Level | Role | Allows |
|---|---|---|
| 0 | ordinary player | no admin commands |
| 1 | moderator (moderatorid) | kick, ban, mute, teleport |
| 2 | owner (ownerid) | additionally change convars and spawn items |
You grant rights by SteamID64:
ownerid 76561198000000000 "Name" "Owner"
moderatorid 76561198000000000 "Name" "Moderator"Removing works the same way:
removeowner 76561198000000000
removemoderator 76561198000000000server.writecfg is no longer required – Rust writes users.cfg itself on every permission change. Plenty of older guides claim otherwise. Second: the new auth level only applies once the player reconnects. That is almost always the reason behind "the command didn't work".Moderating players
| Command | Syntax | Effect |
|---|---|---|
| kick | kick <player> | remove a player from the server |
| ban | ban <player> <reason> [duration] | ban a player |
| banid | banid <SteamID64> <name> <reason> [duration] | ban by SteamID – works offline too |
| unban | unban <player> | lift a ban |
| mute | mute <player> | mute text chat |
| unmute | unmute <player> | unmute text chat |
| mutevoice | mutevoice <SteamID64> | mute voice chat |
| unmutevoice | unmutevoice <SteamID64> | unmute voice chat |
banid is the more reliable route: it works when the player is offline and targets exactly the right person. Names can be changed, SteamIDs cannot.Finding players and pulling information
| Command | Effect |
|---|---|
users | shows the currently connected players |
status | list of connected clients with connection details |
playerlist | retrieve the player list |
sleepingusers | shows sleeping players |
Every moderation action needs a SteamID64, which makes users almost always the first command you run.
Teleport and movement
| Command | Syntax | Effect |
|---|---|---|
| teleport | teleport "player1" "player2" | move player 1 to player 2 |
| teleportpos | teleportpos <x> <y> <z> | teleport to coordinates |
| teleport2me | teleport2me "player" | bring a player to you |
| noclip | noclip | free-fly through walls – F1 console only |
For noclip a key bind saves you opening the console every time:
bind o noclipnoclip off while you are above solid ground, or you drop through the world. Godmode in Rust is likewise a client-side setting and, like noclip, cannot be triggered over RCON.Managing the server
| Command | Syntax | Effect |
|---|---|---|
| save | save | write the world state to disk immediately |
| restart | restart <seconds> | restart with a countdown and announcement |
| quit | quit | shut the server down immediately |
| say | say <message> | message to every player |
save before any restart or intervention. restart with a countdown warns players first – quit stops without warning.A clean restart with five minutes' notice:
save
restart 300Environment: time and weather
| Command | Syntax | Effect |
|---|---|---|
| env.time | env.time <0-24> | set the time of day |
| env.addtime | env.addtime <hours> | fast-forward time |
| weather.rain | weather.rain <0-1> | rainfall intensity |
| weather.fog | weather.fog <0-1> | fog |
| weather.wind | weather.wind <0-1> | wind |
A value of 0 switches that weather off, 1 sets it to maximum. Permanent daylight:
env.time 12Items, entities and events
| Command | Syntax | Effect |
|---|---|---|
| inventory.give | inventory.give <item> <amount> | give yourself items |
| inventory.giveto | inventory.giveto <player> <item> <amount> | give a player items |
| inventory.giveall | inventory.giveall <item> <amount> | give every player items |
| inventory.givebp | inventory.givebp <item> | grant a blueprint |
| entity.spawn | entity.spawn <prefab> | spawn an object at your position |
| heli.call | heli.call | call in the attack helicopter |
| supply.call | supply.call | trigger a supply drop |
Antihack
| Convar | Effect |
|---|---|
antihack.enabled | turn the protections on or off |
antihack.flyhack_protection | protection against fly hacks |
antihack.speedhack_protection | protection against speed hacks |
antihack.noclip_protection | protection against noclip |
Oxide/uMod: plugin permissions
If you run Oxide/uMod, a separate permission system comes with it. Installation and the basics are covered in the Oxide and Carbon section of how to create a Rust server.
| Purpose | Syntax |
|---|---|
| Grant to a player | oxide.grant user <name/SteamID64> <permission> |
| Grant to a group | oxide.grant group <group> <permission> |
| Revoke | oxide.revoke user <name/SteamID64> <permission> |
| Reload a plugin | oxide.reload <PluginName> |
Instead of oxide. the short form o. works too – so o.grant, o.revoke and o.reload.
An example:
o.grant group supporters coolplugin.use
o.reload CoolPlugino.grant user "Max Muster" backpacks.use.Troubleshooting
| Problem | Likely cause and fix |
|---|---|
| Command not recognised | missing rights, a typo, or the wrong namespace – check the prefix |
| Admin rights have no effect | after ownerid the player has to reconnect |
| Rights supposedly gone after a restart | server.writecfg is not needed; if they really are gone, check write permissions on users.cfg |
noclip does nothing over RCON | the command works only in the F1 console |
kick cannot find the player | ambiguous name or player offline – use banid with the SteamID instead |
| Fell through the world after leaving noclip | you need solid ground beneath you when switching it off |
| Item command does nothing | wrong internal item name |
| Changes lost after a crash | run save before any intervention |
Frequently asked questions
How do I become admin on my Rust server? Run ownerid <SteamID64> "Name" "Owner" in the server console or over RCON. Then reconnect once so the auth level applies.
Do I still need server.writecfg after ownerid? No. Rust saves permission changes to users.cfg automatically. Older guides that insist on server.writecfg reflect an outdated state.
Why doesn't noclip work over RCON? Because noclip is tied to your character and can only run in the F1 console. Over RCON there is no character for the command to act on.
How do I ban a player who is offline? With banid <SteamID64> <name> <reason>. Unlike ban, it works regardless of whether the player is currently connected.
How do I restart the server cleanly? First save, then restart <seconds> – for example restart 300 for five minutes' notice. quit stops without any announcement.
How do I set time and weather? Use env.time <0-24> for the clock and weather.rain, weather.fog or weather.wind with values between 0 and 1.
How do I grant plugin permissions? With oxide.grant user <name> <permission> or oxide.grant group <group> <permission>, short form o.grant. Then reload the plugin with oxide.reload <PluginName>.
Related articles
- How to create a Rust server – installation,
server.cfg, ports, Oxide and wipes - Minecraft commands – the same reference for Minecraft servers
- How to create a DayZ server and how to create a Project Zomboid server – more survival servers
Summary
Rust administration runs through three routes – F1 console, server console and RCON – and not every command works on all of them. Permissions need ownerid or moderatorid with a SteamID64, followed by a reconnect; contrary to many guides, server.writecfg is no longer required.
Day to day, a handful of commands carries you: users to find people, banid to ban them, save and restart for an orderly reboot, plus env.time and the weather. commands for the environment. If you would rather not run the machine yourself, you can rent a Rust server.