Last checked: September 25, 2026 against the Facepunch server documentation. Remember: server convars from the F1 console need the prefix sv (for example sv weather.rain 0), otherwise they only take effect client-side.
Rust server commands help you administer your own server in a controlled way: you assign rights, check players, save the world, change settings, teleport to problems and carry out wipes in a targeted manner. This guide shows the most important commands for operating a paid hosted Rust server, with clear verification and troubleshooting.
Requirements
Before you run commands, you should have access to the server console or RCON. At game-serverhosting, you typically use the dashboard with the live console for this; an external RCON client additionally requires an explicitly available, secured port assignment. Enabling RCON alone does not guarantee public access. For permission commands, you need the SteamID64 of the person concerned.
As the official primary source, Facepunch's Rust documentation for server setup mentions, among other things, the use of server.cfg, RCON and admin rights: Documentation at wiki.facepunch.com. Facepunch's command overview also lists many of the commands used here: Documentation at wiki.facepunch.com.
Connecting via RCON
Connect to the server console via the dashboard or an external client. If your setup requires an explicit RCON login, you use:
# rcon.login is legacy RCON; WebRCON (rcon.web 1, default) authenticates on connect
In everyday hosting, the dashboard console is often the calmer way, because you see server status, logs and inputs in one place. You should not share RCON credentials publicly and should only give them to team members who really need to administer.
Server Management
These commands affect the running server operation. Use them deliberately, especially when players are online.
| Command | Description |
|---|---|
server.save |
Save the world |
server.writecfg |
Save the config |
quit |
Save and shut down the server (restart with countdown) |
server.hostname "Name" |
Change the server name |
server.maxplayers 100 |
Vendor example for the player limit; at GSH the booked slot count applies at startup |
server.worldsize 3500 |
Map size |
server.save is useful before maintenance, restarts or planned interventions. With server.writecfg you write changed server variables into the configuration, as far as they are meant for it. In the server documentation, Facepunch notes that for many variables a server.cfg in the folder rust/server/server.identity/cfg/ is the suitable place.
If you want to dive deeper into planning, RAM and settings, the internal guide Rent a Rust Server: RAM, Settings & Plugins is a good next step.
Player Management and Permissions
For moderation you first need an overview. status shows you active player information. For administrative commands, use the SteamID64 rather than names where possible, because names can look similar or be changed.
| Command | Description |
|---|---|
status |
Show online players |
kick <name/id> "reason" |
Kick a player |
ban <steamid64> "Name" "reason" [duration] |
Ban an online player; banid also works offline; duration e.g. 7d |
unban <steamid64> |
Unban a player |
banlist |
Show the ban list |
ownerid <id> "Name" |
Grant owner rights |
moderatorid <id> "Name" |
Moderator rights |
removeowner <id> |
Remove an owner |
Owner rights are the highest administrative level. Moderator rights are enough for many operational tasks. So grant owner sparingly. According to Facepunch, reconnecting may be necessary after setting admin or moderator rights for the auth level to take effect.
A typical sequence is: run status, copy the SteamID64, set ownerid or moderatorid, reconnect, then verify with a harmless admin action.
World Commands
World commands change the environment, time or spawns. They are useful for tests, events and error analysis, but can affect the player experience.
| Command | Description |
|---|---|
env.time 12 |
Set the time of day (0-24) |
weather.fog 0 |
Disable fog |
weather.rain 0 |
Disable rain |
weather.cloud_coverage 0 |
Remove clouds (-1 = automatic weather) |
spawn.fill_populations |
Respawn NPCs |
spawn.fill_groups |
Refill loot containers and spawn groups |
It is best to use such commands outside critical PvP situations or announce events beforehand. If you plan wipes regularly, the Rust Wipe Calendar 2026 additionally helps you classify force wipes and blueprint wipes properly.
Teleport and Noclip
Teleport commands are especially helpful when players are stuck, a suspicion needs to be checked or you want to test coordinates.
noclip # Fly through walls
teleport <name> # Teleport to a player
teleportpos "0, 100, 0" # Teleport to coordinates (also via RCON)
teleport2me <name> # Teleport a player to you
When moderating, you should use teleports in a traceable way. For exact positions, coordinates or SteamID64 are more robust than freely typed names. If you are preparing map planning, the guide Finding a Rust Server Map Seed fits well.
Giving Items
Item commands are suitable for tests, events or restoration after a clearly documented problem. They should not be used uncontrolled in live operation.
inventory.give <item> <amount> # only in the in-game F1 console, not via RCON
inventory.giveto <name> <item> <amount>
inventory.giveall <item> <amount>
Example: inventory.give rifle.ak 1
Check item short names before use. If a command does not work, it is often due to a wrong item name, missing permissions or the target player not being found unambiguously.
Performing a Wipe
A wipe works in the folder of the active server.identity and may only be done after a controlled stop. Back up the complete identity folder, including save and blueprint files, in a separate location. Then confirm the desired scope: map wipe or additionally a blueprint wipe.
| Wipe scope | Affected data in the active identity folder |
|---|---|
| Map wipe | Current world saves and their backups; blueprints retained |
| Blueprint wipe | Additionally the associated player.blueprints.*.db |
Check the actual file names before any file action. Do not use a blanket *.db pattern: it can also hit other player data and Rust+ assignments. Only restart after checking the backed-up data.
Use a dedicated wipe function only if it explicitly supports the desired scope. A scheduled restart alone is not a wipe. Document the identity, backup, deleted data scope and the subsequent world/blueprint test.
Verifying the Result
After admin commands, first check the console for error messages. Then check in the game whether the change is visible: rights take effect, players were moderated, time or weather fit, items arrived or the world was saved. For configuration changes, a restart or reconnect is additionally possible, depending on the specific command.
Troubleshooting
If a command is not recognized, check spelling, permissions and context. Some commands belong in the server console, others work as admin in the client or with a server prefix. If admin rights do not take effect, reconnect and check the SteamID64. If RCON does not connect, check the password, port, firewall and whether RCON is correctly enabled on the server. For wipe problems, check whether you are editing the right server.identity and thus the right server folder.
FAQ
Which Rust server commands do I need first as an admin?
To get started, status, ownerid, moderatorid, server.save, server.writecfg, kick, ban and unban usually suffice. With them you can set permissions, manage players and secure the server state.
Do I have to reconnect after ownerid or moderatorid?
Often yes. When setting up admin rights, Facepunch describes that a reconnect may be necessary for the auth level to visibly take effect. Afterwards, check the console and test a harmless admin action.
Should I manage players by name or SteamID64?
Use the SteamID64 whenever possible. Names can be similar, contain special characters or be changed. A SteamID64 is more unambiguous and reduces the risk of kicking, banning or granting rights to the wrong player.
What is the difference between a map wipe and a BP wipe?
A map wipe removes world state such as buildings and items, while blueprints are retained. A BP wipe additionally deletes blueprint data. Only perform such interventions in a planned manner and inform your community beforehand.
Can I use all commands directly in the game-serverhosting panel?
The live console is intended for typical server commands. However, individual actions depend on Rust, server state and permissions. If a command does not take effect, check the console output and whether the command is suitable for the current context.