Rust Admin Setup: ownerid, moderatorid, users.cfg and Moderation Commands
On a Rust server, admin rights are granted by SteamID64. ownerid gives the highest authorisation level and moderatorid gives the lower one. You can run them on the Console tab, or manage the same list from the Admins and moderators area of the Configs tab.
This guide covers getting the right ID, the commands, where the list is saved, and the moderation commands worth knowing. It was checked on 2026-11-15 against Facepunch's server documentation as quoted by hosting guides, and three host guides. The sources disagree on exactly what a moderator may do, so that is marked below. For the rest of your server.cfg, see the Rust server settings guide.
- A SteamID64 is a 17 digit number starting with
7656119. It is not the player's name. - Run
ownerid STEAMID64 "Name" "Reason"ormoderatorid STEAMID64 "Name" "Reason". The name and reason are optional. The player should reconnect afterwards. - Admins are stored in
users.cfgin the server'scfgfolder. If you edit it by hand, stop the server first, because Rust rewrites it. - Owner is authorisation level 2 and moderator is level 1. Give out moderator unless someone truly needs full control.
kick,ban,banidandunbancover most moderation.
On this page
Get the SteamID64
Rust identifies players by SteamID64: 17 digits, starting with 7656119. If the player has a custom profile URL, their ID is not in it, so ask them for the number or use a Steam ID lookup tool in your own browser. The status command on the Console tab lists connected players, and the ID is shown alongside each name. Copy the number exactly, because a single wrong digit gives admin to a stranger or to nobody.
Add an owner or moderator
- Open the Console tab
Go to panel.chicagoservers.co, choose your Rust server and open Console. The server must be running.
- Run the command
Use
owneridfor full authorisation ormoderatoridfor the lower level. The quoted name and reason are optional.ownerid 76561198000000000 "PlayerName" "head admin" moderatorid 76561198000000001 "OtherName" "mod" - Ask them to reconnect
Authorisation is read when a player joins, so they need to reconnect to see it.
- Test it
In game, press F1 to open the console and run a harmless admin command, such as
status.
Where admins are saved
Admin entries are stored in users.cfg, in the cfg folder for your server's identity, for example server/<identity>/cfg/users.cfg. A host quoting Facepunch says the file is updated automatically when you run ownerid or moderatorid. Other host guides tell you to also run server.writecfg, which saves settings and is harmless to run, so run it if you want to be sure.
- Edit by hand only when the server is stopped. A running server writes this file and can overwrite your edit.
- Bans are kept in
bans.cfgin the same folder, also shown under Bans on the Configs tab. - Use the Files tab to edit, or SFTP. See how to use SFTP.
Owner or moderator?
Owner is authorisation level 2 and moderator is level 1. Hosting guides disagree about how different they are. One says moderators can kick, ban and use admin tools but not every console command, and cannot add other admins. Another says both levels can run the admin commands, and that the differences are in-game ownerid and seeing player IPs in status. Test with your own account before trusting anyone with the role. The safe habit is simple: give moderator to staff, and owner only to people who can be trusted with the whole server.
| Command | What it does |
|---|---|
removeowner STEAMID64 | Removes level 2 access. |
removemoderator STEAMID64 | Removes level 1 access. |
Moderation commands
| Command | What it does |
|---|---|
kick "name" "reason" | Removes a player and announces it. |
kickall "reason" | Kicks everyone. |
ban "name" "reason" | Bans and kicks an online player. |
banid STEAMID64 "name" "reason" | Bans by ID, which works for players who are offline. One host notes it does not kick or announce. |
unban STEAMID64 | Lifts a ban. |
bans | Lists bans. |
say "message" | Broadcasts a message to the server. |
server.save | Forces a save. |
Hosting guides also list commands for teleporting, muting and giving items, such as teleport, admin.mutechat and inventory.give. Lists differ by game version, so use the find command on the Console tab to check the exact name on your server before running one. Commands in the F1 console are typed without a leading slash.
Security checklist
- Use a strong RCON password on the Startup tab, because RCON can run admin commands.
- Give out owner rarely and review the list on the Configs tab from time to time.
- Remove access with
removeownerorremovemoderatoras soon as someone leaves your staff. - Plugins such as Oxide or Carbon have their own permission systems. See installing Oxide or Carbon.
Looking for a host? See Rust server hosting.
Frequently asked questions
How do I make someone admin on a Rust server?
Run ownerid STEAMID64 on the server console, or moderatorid for the lower level, then ask the player to reconnect.
What is a SteamID64 for Rust?
A 17 digit number starting with 7656119 that identifies a Steam account. Rust uses it for admin and ban commands.
Where does Rust store admins?
In users.cfg in the cfg folder for your server identity. Edit it only while the server is stopped.
What is the difference between ownerid and moderatorid in Rust?
Owner is authorisation level 2 and moderator is level 1. Sources differ on exactly what moderators cannot do, so test before trusting the role.
How do I ban a Rust player who is offline?
Use banid with their SteamID64 and a reason. Use unban STEAMID64 to lift it later.