Rust server commands help you administer your own server in a controlled way: you assign permissions, check players, save the world, change settings, teleport to problems, and run wipes deliberately. This guide shows the most important commands for running a paid hosted Rust server with clear checks 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; alternatively, an external RCON client works if RCON is configured correctly. For permission commands, you need the SteamID64 of the person in question.
As an 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 through the dashboard or an external client. If your setup requires an explicit RCON login, use:
rcon.login <password>
In everyday hosting, the dashboard console is often the calmer option because you see server status, logs, and input in one place. You should not share RCON credentials publicly and should only give them to team members who truly need to administer the server.
Server Management
These commands affect ongoing server operation. Use them deliberately, especially when players are online.
| Command | Description |
|---|---|
server.save |
Save the world |
server.writecfg |
Save the config |
server.stop |
Stop the server |
server.hostname "Name" |
Change the server name |
server.maxplayers 100 |
Max players |
server.worldsize 3500 |
Map size |
server.save is useful before maintenance, restarts, or planned interventions. With server.writecfg, you write changed server variables to the configuration, provided they are intended for that. In the server documentation, Facepunch points out that for many variables, a server.cfg in the rust/server/server.identity/cfg/ folder is the appropriate place.
If you want to go deeper into planning, RAM, and settings, the internal guide Rent a Rust Server: RAM, Settings & Plugins is a suitable next step.
Player Management and Permissions
For moderation, you first need an overview. status shows you active player information. For administrative commands, use SteamID64 instead of names whenever possible, because names can look similar or be changed.
| Command | Description |
|---|---|
status |
Show online players |
kick <name/id> "Reason" |
Kick a player |
ban <name/id> "Reason" |
Ban a player |
unban <steamid64> |
Unban a player |
banlist |
Show ban list |
ownerid <id> "Name" |
Grant owner rights |
moderatorid <id> "Name" |
Moderator rights |
removeowner <id> |
Remove owner |
Owner rights are the highest administrative level. Moderator rights are enough for many operational tasks. Therefore, grant owner rights sparingly. According to Facepunch, after setting admin or moderator rights, reconnecting may be necessary for the auth level to take effect.
A typical sequence is: run status, copy the SteamID64, set ownerid or moderatorid, reconnect, then check with a harmless admin action.
World Commands
World commands change the environment, time, or spawns. They are useful for tests, events, and troubleshooting, but they can affect the player experience.
| Command | Description |
|---|---|
env.time 12 |
Set the time (0-24) |
weather.fog 0 |
Disable fog |
weather.rain 0 |
Disable rain |
weather.clouds 0 |
Remove clouds |
spawn.fill_populations |
Respawn NPCs |
spawn.fill_groups |
Refill animal spawns |
It is best to use commands like these outside critical PvP situations or announce events in advance. If you plan wipes regularly, the Rust Wipe Calendar 2026 also helps you classify force wipes and blueprint wipes cleanly.
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
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 Find a Rust Server Map Seed fits this topic.
Giving Items
Item commands are suitable for tests, events, or recovery after a clearly documented problem. They should not be used without control during live operation.
inventory.give <item> <amount>
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 an incorrect item name, missing permissions, or the target player not being found unambiguously.
Running a Wipe
Depending on the scope, a wipe deletes world files or additionally blueprint data. Back up relevant data beforehand and only perform file operations if you are sure you are working in the correct server directory.
# In the server directory:
# Map wipe (buildings/items gone, BPs remain):
rm server/my_server/*.sav*
rm server/my_server/*.map
# BP wipe (additional):
rm server/my_server/*.db
At game-serverhosting, you can plan wipes conveniently through the dashboard or scheduler. During operation, this is often easier to trace than manual file operations via shell because times and processes can be controlled more cleanly.
Checking the Result
After admin commands, first check the console for error messages. Then check in-game whether the change is visible: permissions work, players were moderated, time or weather is correct, items arrived, or the world was saved. For configuration changes, a restart or reconnect may also be 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 an 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 correct server.identity and therefore the correct server folder.
Check, Limits, and a Safe Way Back
The guide “Rust Server Commands – Admin Commands for Your Server” applies to the server type described in the article and the version status visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them.
Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and check it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Stop and Way Back |
|---|---|---|
| Server start | The server reaches the ready-to-operate state without a new error message. | If startup errors occur, revert the change and restore the latest backup. |
| Connection test | A test account can connect using the address shown in the panel. | If version or connection errors occur, compare the version, port, and allowances again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore the backed-up files. |
A successful individual test is not a guarantee of performance or availability. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.
FAQ
Which Rust server commands do I need first as an admin?
To start, status, ownerid, moderatorid, server.save, server.writecfg, kick, ban, and unban are usually enough. With these, you can set permissions, manage players, and secure the server state.
Do I need to reconnect after ownerid or moderatorid?
Often yes. When setting up admin rights, Facepunch describes that a reconnect may be required for the auth level to visibly take effect. After that, check the console and test a harmless admin action.
Should I manage players by name or SteamID64?
Use SteamID64 whenever possible. Names can be similar, contain special characters, or be changed. A SteamID64 is more unique 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 remain. A BP wipe additionally deletes blueprint data. Only perform such interventions in a planned way 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. Individual actions still depend on Rust, the 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.