How toRust

How to Make Yourself Admin on a Rust Server (ownerid)

How to make yourself admin on your Rust server with ownerid and moderatorid, save it with server.writecfg, and use admin commands and Oxide admin groups.

Updated Sep 30, 2026 · 4 min read

On this page

To make yourself admin on a Rust server, run ownerid followed by your SteamID64 in the server console, then server.writecfg to save it, and reconnect. That gives you owner level access to admin commands like noclip, kick and ban from your own F1 console. This guide shows how to find your SteamID64, the difference between owners and moderators, the most useful admin commands and how Oxide admin groups fit in.

Short answer

In the server console (not your game console), run:

ownerid 76561198000000000 "YourName"
server.writecfg

Swap in your own SteamID64, then disconnect and join again. Done.

Step 1: Find your SteamID64

Your SteamID64 is a 17 digit number that starts with 7656.

  • Open Steam, click your name, then Profile. If your profile address ends in a long number, that is it.
  • If you set a custom profile URL, paste the profile link into any SteamID lookup site to get the number.
  • Already on the server? Type status in the server console. It lists everyone connected with their SteamID64.

Use the long number. Names and custom URLs do not work with ownerid.

Step 2: Run ownerid in the server console

You need the server's own console for the first admin, because nobody on the server has the rights to grant them yet.

  • Self hosted: type it in the RustDedicated window, or through an RCON tool.
  • GamezServers: open your server, go to the Console tab and type it at the bottom. The console accepts any command, so no RCON setup is needed.
ownerid 76561198000000000 "YourName" "Server owner"

The name and the reason in quotes are optional labels. Then run:

server.writecfg

This writes the change to cfg/users.cfg inside your identity folder. Skip it and your admin rights vanish at the next restart.

Step 3: Reconnect

Admin rights apply when you join, so disconnect and join again. Press F1 and try noclip. If you start flying, it worked.

Owner vs moderator

Owner (ownerid) Moderator (moderatorid)
Auth level 2 1
Kick, ban, teleport, noclip Yes Yes
Add or remove other admins Yes No

Give your co-owner ownerid and trusted friends moderatorid:

moderatorid 76561198000000001 "FriendName"
server.writecfg

To take rights away, use removeowner or removemoderator followed by the SteamID64, then server.writecfg.

Useful admin commands

Type these in your F1 console once you are an admin:

Command What it does
noclip Fly through walls. Type again to stop
debugcamera Free camera, handy for checking bases
god true No damage. god false to turn off
env.time 12 Sets the time of day to noon
teleport "Name" Teleports you to a player
teleport2me "Name" Brings a player to you
status Lists players with their SteamID64
kick "Name" "reason" Kicks a player
ban "Name" "reason" Bans a player who is online
banid 7656... "Name" "reason" Bans by SteamID64, even when offline
unban 7656... Removes a ban

Use them with care on a server your friends share. Nothing ends a friend group's wipe faster than an admin flying around in god mode.

Admin with Oxide or Carbon plugins

Rust's ownerid and plugin permissions are separate systems. Being owner does not automatically give you every plugin's admin features. Oxide and Carbon have their own admin group, and plugins grant extra powers through it. Add yourself:

oxide.usergroup add 76561198000000000 admin

Many plugins also treat Rust owners as admins, but adding yourself to the group covers the ones that do not. On Carbon, use c.usergroup add instead. More on permissions in how to install Rust plugins with Oxide or Carbon.

Common problems

  • "You do not have permission" after ownerid: you have not reconnected yet, or you used the wrong SteamID64 (a friend's, or the short Steam3 format).
  • Admin gone after a restart: you skipped server.writecfg.
  • Admin gone after a wipe: a wipe should not touch cfg/users.cfg. If it did, the whole identity folder was deleted. Run ownerid again. See how to wipe a Rust server for which files to keep.
  • Typed ownerid in your own F1 console: it does nothing until you are already an admin. Use the server console for the first one.

The easy way to reach the server console

On a self hosted server you need the machine in front of you or an RCON tool set up with the right port and password to run that first ownerid. With a GamezServers Rust server, the console sits in your browser tab, and friends who split the bill can use it too from their own dashboard.

FAQ

How do I make someone else admin on my Rust server?

Run moderatorid (or ownerid) with their SteamID64 in the server console or your F1 console as owner, then server.writecfg. They reconnect to get the rights.

What is the difference between ownerid and moderatorid?

Owners have auth level 2 and can manage other admins. Moderators have auth level 1 and can kick, ban and use most admin tools, but cannot add admins.

Do I need Oxide to be admin in Rust?

No. ownerid is built into Rust. Oxide only adds plugin permissions on top.

Why does noclip not work?

You are not an admin yet, or you did not reconnect after running ownerid. Check with status that your SteamID64 matches.

Skip the setup. Your Rust server, live in 60 seconds.

Plans first month from $9.99. No command line, cancel any time.

Deploy Rust

Keep reading