← Blog

Rust console: RCON commands for bans, wipes and performance

Par Benjamin Dayan · PDG

· Mis à jour le November 18, 2026 · Lecture 7 min

Contents
Server administrator typing Rust console commands into an RCON panel on a dark screen during a wipe night

Rust console commands: what are we talking about?

Rust console commands run in three places on a PC server: the in-game F1 console, the server console (your panel) and RCON, the password-protected remote access. Most commands in this cheat sheet work in all three; perf and client.connect only work from the F1 console. Rust Console Edition (PlayStation/Xbox) is a different game and offers none of this.

This guide is for whoever runs a server: moderation, permissions, saves, wipes and performance.

In brief

  • The F1 console only accepts admin commands if your account is an owner or moderator.
  • ownerid and moderatorid grant the rights. Run server.writecfg afterwards so they survive a restart.
  • banid bans an offline player, while ban only works on someone who is connected.
  • Forced wipe lands monthly; check the schedule for the exact date. A map wipe deletes the .map and .sav files, and a BP wipe deletes the player.blueprints.*.db files.
  • serverinfo gives a reliable view of server FPS, players and entities.

Rust Console Edition (PS4/PS5, Xbox): this is a separate version of the game from the PC one. As far as we know, it has no F1 console, no RCON and no Oxide. Nothing below applies to it.

Opening the console and enabling RCON

There are three entry points, each with its own use:

  • F1 in game: the client console. Admin commands only respond if you are an owner or moderator.
  • Server console: the terminal or the panel. No in-game authentication is needed, so it is the simplest way to make yourself owner the first time.
  • RCON: remote access. It is enabled with launch parameters, and the Valve developer wiki page on the Rust dedicated server lists the values. The RCON port is set with the rcon.port parameter below.
+rcon.port 28016 +rcon.password "YourLongPassword" +rcon.web 1

+rcon.web 1 enables WebRCON (WebSocket), the recommended mode. Choose a long password, never post it on Discord (not even in a "staff" channel), and don't open the port to the whole internet without a reason.

With Rust Server Hosting: rent your Rust server from £7.46/mo, none of this needs configuring to get started. The real-time FlyPanel console sends your commands straight to the server, so there is no external RCON client to install.

Granting admin rights: ownerid and moderatorid

The syntax is the same for both levels. The steamID64 is the player's 17-digit identifier, which you can read in the id column of the status or players command.

ownerid 76561198000000000 "Username" "founder"
moderatorid 76561198000000001 "Username2" "mod"
server.writecfg
Command Effect
ownerid <steamID64> "Username" "reason" Full rights (authlevel 2)
moderatorid <steamID64> "Username" "reason" Moderation rights (authlevel 1), without removeowner
removeowner <steamID64> Removes an owner
removemoderator <steamID64> Removes a moderator

The most common trap is an ownerid that vanishes on restart. Rights live in users.cfg, and a uMod community thread reports exactly this problem: the ownerid disappears after a restart, with no confirmed fix. Running server.writecfg after the command writes the rights to disk. Some versions seem to write them on their own, but run the command anyway because it costs nothing.

Three other details save you from nasty surprises:

  • The player has to reconnect for their new level to apply.
  • Put usernames in quotation marks, because a space in a name breaks the command.
  • With Oxide/uMod, plugin permissions are managed separately: oxide.grant user <name|id> <permission>. An owner does not automatically hold every Oxide permission.

Banning, unbanning and kicking a player

Command Use Example
kick <name|id> "reason" Kicks a connected player kick "Jack" "AFK at spawn"
ban <name> "reason" Bans a connected player ban "Jack" "cheating"
banid <steamID64> "name" "reason" Bans an offline player banid 76561198000000002 "Jack" "cheating"
unban <steamID64> Lifts a ban unban 76561198000000002
banlist Short list of banned players banlist
banlistex Detailed list with reasons banlistex

Target the steamID rather than the username. Names change, appear twice or contain characters that make the command fail. Bans are stored in bans.cfg. As with rights, finish with server.writecfg if you want to be sure they persist.

Always write a proper reason. When a player disputes a ban on Discord, banlistex saves you from digging through chat history.

Forcing a server save

server.save forces the map to be written to the .sav file immediately. The automatic frequency is set with server.saveinterval, in seconds.

server.save
server.saveinterval 600

Run server.save before a restart, an update or a plugin install. Otherwise you risk losing whatever players have built since the last save.

This command saves the state of the world, not your whole server (configs, plugins, data). People confuse the two all the time. For a real safety net, you want a backup, available as an option on the pricing page at +£1.65/month, with restore from the panel.

Preparing a wipe from the console

A map wipe resets the world (terrain, bases, loot) but leaves blueprints alone. A BP wipe also erases what players have learned. Facepunch's official forced wipe happens monthly, according to this schedule. Check the date for your month before announcing anything.

Pre-wipe checklist

  1. Warn players: say "Wipe in 10 minutes, please log off".
  2. Save: server.save.
  3. Persist rights and settings: server.writecfg.
  4. Shut the server down cleanly: quit.
  5. Take a backup before deleting anything.
  6. For a new map, change server.seed and, if needed, server.worldsize. Check the range of values server.worldsize accepts before setting it. On FlyPanel, seed and size are changed from the panel.
  7. With the server stopped, delete the files: .map and .sav for a map wipe, plus player.blueprints.*.db for a BP wipe.

The classic mistake is deleting a .db file out of habit and triggering a BP wipe nobody announced. Read the file names twice before you erase anything. If you can't work out how to delete them in the panel, the team is reachable on Discord.

After the wipe: checking everything comes back

Watch the console at startup: map generation first, then any plugin errors. With Oxide/uMod, o.version confirms which version has loaded, and oxide.reload PluginName restarts a stubborn plugin without rebooting the server.

Finish with a real test by connecting with client.connect IP:port from F1. Our page on how to join a Rust server walks you through it.

Checking performance from the console

Command Where What it gives you
serverinfo Server Server FPS, players, entities, memory
status / players Server Connected players, each one's ping
perf 1 Client (F1) FPS and latency overlay on the player's side (perf 0 hides it)
gc.collect Server Forces a memory clean-up: run it outside peak hours

Read these figures together. Server FPS that drops as the entity count climbs points to an overloaded map or hungry plugins. High ping for a single player comes from their connection, not from your machine.

Rust leans heavily on the power of a single core, which is why Fly-Serv's Rust offer runs on a Ryzen 9 7950X3D (5.7 GHz, 128 MB of V-Cache).

Rust console commands to keep handy

Category Command Effect
Rights ownerid <id> "name" "reason" Adds an owner
Rights moderatorid <id> "name" "reason" Adds a moderator
Rights removeowner <id> Removes an owner
Rights server.writecfg Writes rights and settings to disk
Moderation kick <name|id> "reason" Kicks a player
Moderation ban <name> "reason" Bans a connected player
Moderation banid <id> "name" "reason" Bans an offline player
Moderation unban <id> Unbans
Moderation banlistex Detailed bans
Saving server.save Immediate map save
Wipe server.seed <n> Seed for the next map
Wipe server.worldsize <n> Map size
Announcement say "message" Message to all players
Performance serverinfo Server FPS, entities, memory
Oxide oxide.reload <plugin> Reloads a plugin
Oxide oxide.grant user <id> <perm> Grants a permission

The full, up-to-date list is the one on Facepunch's official wiki. Check it whenever a command stops behaving as expected after an update.

Questions fréquentes

How do I open the console in Rust?

Press F1 in game. On a server, admin commands only work if you are an owner or moderator. On the server side, use the panel console or an RCON client.

Why does my ownerid disappear after a server restart?

Rights are written to users.cfg, but not always automatically. Run server.writecfg straight after ownerid, then reconnect so the level applies.

What is the difference between ban and banid in Rust?

ban targets a player who is currently connected, identified by name. banid takes a steamID64 and also works for an offline player. Either way, the steamID is more reliable than a username.

When is the forced wipe on Rust servers?

Monthly, alongside the Facepunch update. Check the exact date for the month on a wipe calendar before you announce it.

Can you use console commands on Rust Console Edition (PS5, Xbox)?

As far as we know, no: that version has no F1 console and no RCON. These commands apply to Rust on PC and its dedicated servers.

Which command shows the Rust server's FPS?

serverinfo shows the server framerate along with players, entities and memory. perf 1 in F1 shows your client-side FPS, which is a different measurement.

Try these commands on a real server

Run through them before your next wipe: add yourself as owner, do a server.save, then a serverinfo. On Rust Server Hosting: rent your Rust server from £7.46/mo, everything is typed into the FlyPanel console. You choose the seed and map size, install Oxide/uMod in one click and host up to 200 players, and Anti-DDoS is included for wipe nights. There is no commitment, and delivery takes under 60 seconds. If your community plays something else too, take a look at all our game servers.

Read next