How to Become Admin on a Rust Server (Owner and Moderator Commands)

Rust grants administrative access through server commands, not an in-game settings menu. Run ownerid STEAMID64 "Name" "Note" for full owner access (auth level 2), or moderatorid STEAMID64 "Name" "Note" for moderator access (auth level 1). Your identifier must be the 17-digit decimal SteamID64 that normally starts with 7656. The first grant must come from the server console, RCON, or your hosting panel’s console because you cannot use privileged in-game commands before you have a permission level.

Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.

What you need before granting Rust admin access

Have these items ready before entering a command:

• Access to the live server console, an authenticated RCON session, or the console supplied by your hosting panel.
• The target player’s 17-digit decimal SteamID64. A Rust username is not an acceptable replacement, and a hexadecimal Steam identifier is not the format used by these commands.
• The exact server instance you intend to administer. A command sent to a test server, a different instance, or a stopped server will not give access to the live world.
• A decision about whether the account should be an owner or a moderator. Use the smallest permission level that meets the job.

The first command is normally issued while the server is running. If your host exposes several consoles, use the one attached to the Rust instance rather than a general machine terminal.

#	Preview	Product	Price
1		Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key...	$25.00	Buy on Amazon
2		Rust Video Game Notebook	$15.00	Buy on Amazon
3		Rust Game Props Large Furnace (S)	$14.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Owner and moderator permissions

Rust uses authorization levels rather than a single “admin” switch. The two standard grants are:

Availability of commands such as noclip, god, spawn and give at level 1 varies by server version or configuration. Treat those abilities as version- or configuration-dependent instead of promising them to every moderator. Test the commands on your server and keep the account at level 1 unless broader control is required.

#1 Best Overall

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

• Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
• High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
• Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
• Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
• NOT a sticker*

$25.00

Buy on Amazon

Find the correct SteamID64

The identifier in an authorization command is the account’s SteamID64 in decimal form. It is a 17-digit number that generally begins with 7656. The value is not:

• the player’s display name or Rust username;
• the short name shown in a chat list;
• the hexadecimal form of a Steam ID; or
• a name copied from a clan or server nickname.

Copy the decimal SteamID64 from the player’s Steam profile information or from a reliable identifier tool, then check the result manually. Count the digits and confirm that it begins with 7656. If the value contains letters, punctuation, or fewer than 17 digits, stop and obtain the decimal form before running the grant.

Names and notes in the command are labels for people reading the authorization list. They do not identify the account. Keep the name short and recognizable, and use the note to record a role or reason such as “primary owner” or “event moderator.”

Grant full owner access from the console

Use the owner grant when the person needs the highest standard authorization level or must appoint other administrators.

1. Open the Rust server console, an authenticated RCON console, or the hosting panel’s Rust console.
2. Enter the command with the decimal SteamID64 and optional quoted labels:
   ownerid STEAMID64 "Name" "Note"
3. Submit the command and watch for the console response. If the console reports an unknown command, a malformed argument, or a permission error, do not assume the grant succeeded.
4. Have the player disconnect and reconnect if the server does not expose the new commands immediately. Then test one harmless administrative command appropriate to the role.
5. Check the authorization file as described below. This confirms that the grant was written to the instance you edited.

Replace STEAMID64 with the actual number. For example, the structure is a command name followed by the 17-digit number, then a quoted display name and quoted note; do not literally submit the word STEAMID64.

An owner grant is not made through a Rust pause menu or player list. If you are trying to type ownerid in chat before receiving any authorization, it will fail because the account has no authority yet. Start in the external console, RCON, or panel console.

Grant moderator access instead

Use moderator access for staff who need routine player-management tools without owner-level administration.

1. Open the server console, RCON, or panel console.
2. Run:
   moderatorid STEAMID64 "Name" "Note"
3. Confirm that the console accepts the command and that the account appears in the authorization data.
4. Ask the moderator to reconnect, then test the moderation functions your server version allows, such as kick, ban and teleport.

Do not substitute ownerid merely because some moderator commands are unavailable. The two levels are intentionally different, and extra admin-style abilities at level 1 vary by server version and configuration. If a moderator genuinely needs owner-only functions, promote the account deliberately and record that decision.

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

Why the first grant must come from outside the game

Privileged commands are gated by the same authorization system you are trying to configure. A player who has not yet been assigned level 1 or level 2 cannot bootstrap their own access by entering an admin command in chat or the in-game console. The initial command therefore has to come from a channel that already controls the server:

• Dedicated server console: the terminal or control console attached to the Rust process.
• RCON: a remote console session authenticated with the server’s RCON credentials.
• Hosting-panel console: a web control panel’s command console for that specific Rust instance.

After the grant is accepted, reconnect and use the in-game console only for commands your new level permits. If an RCON command appears to run but no authorization is visible, verify that RCON is connected to the intended server and identity rather than a different instance.

Confirm that the grant persisted

Do not rely solely on a success message. Inspect the server’s users.cfg file and look for an entry containing the SteamID64 and the corresponding grant. Whether ownerid, moderatorid, removeowner and removemoderator write users.cfg immediately depends on the server version or configuration. Use a verification-first procedure:

1. Run the grant command.
2. Open users.cfg for the same server identity.
3. If the new line is present, record the change and test the account.
4. If the line is missing, run server.writecfg from the server console or RCON.
5. Open users.cfg again and confirm that the entry now exists before restarting or changing anything else.

Never edit a file on a neighboring server and assume the live server will read it. The file must belong to the instance that accepted the command.

Locate users.cfg

File paths depend on the server identity. For the identity main, configuration is under server/main/cfg/, alongside files such as server.cfg and ban data. A custom identity changes that path. Hosting panels may present the same directory through a file manager with a different top-level label.

Use the panel’s file browser or the directory configured for the Rust service, then look for cfg/users.cfg. If you cannot find it:

• check the active identity name in the startup configuration;
• look for another server/<identity>/cfg/ directory;
• make sure you are viewing the live server’s files rather than a backup or staging copy; and
• run server.writecfg, then refresh the listing after the server has processed it.

Do not infer a universal path from one host. The identity setting is the part that determines where the file belongs.

Add an administrator by editing users.cfg

Editing the file is an alternative when console access is inconvenient, but it requires a reliable backup and careful targeting. Add one authorization entry per user using the SteamID64 and the appropriate command name. The conceptual forms are:

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

ownerid STEAMID64 "Name" "Note"
moderatorid STEAMID64 "Name" "Note"

1. Stop changes to the file while you edit it; if your panel offers a server stop control, use it according to the host’s procedure.
2. Download or copy the existing users.cfg so you can restore it if formatting is damaged.
3. Add the line for the correct SteamID64. Keep the command name and numeric ID exact.
4. Save the file as plain text without adding rich-text formatting or extra characters.
5. Start or reload the server through the host’s normal control, then confirm the account in-game and in the file.

Because hosts differ in how they reload configuration, the console method is easier to audit. If a hand-edited line does not take effect, return to the server console, issue the grant command, and verify the resulting file.

Remove or change access

Use the matching removal command with the same SteamID64 when a staff member leaves or should be downgraded:

• removeowner STEAMID64 removes an owner grant.
• removemoderator STEAMID64 removes a moderator grant.

Run the removal from the server console, RCON, or another channel that has sufficient authority. Then inspect users.cfg. If the old line remains, use server.writecfg and check again. A person who has both owner and moderator entries may retain access through the remaining entry, so remove every grant that should no longer apply.

To downgrade an owner to moderator, remove the owner entry first, confirm it is gone, then add the moderator entry. This two-step approach makes the resulting permission state unambiguous and easier to audit.

Troubleshoot a failed or ineffective grant

Operate administrator access safely

Owner access can appoint additional administrators, so treat an owner SteamID64 as a high-impact credential. Keep a private record of who received level 2, when it was granted, and why. Use moderator level 1 for staff whose work is limited to player management. Do not publish RCON credentials in chat, screenshots, or public configuration snippets.

When a staff member changes role, remove the old grant instead of leaving historical entries in place. After every addition or removal, verify both the file and the actual in-game behavior. This catches typographical errors, wrong-server edits, and persistence problems before they affect a live community.

Use notes that identify a role without exposing sensitive information. A note such as “weekend moderator” is useful to operators; a password, RCON secret, or private contact detail does not belong in users.cfg.

Quick Recap

Bestseller No. 1

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.; NOT a sticker*

$25.00

Bestseller No. 2

Rust Video Game Notebook

$15.00

Bestseller No. 3

Rust Game Props Large Furnace (S)

Acrylic Painting Pla Plastic

$14.99

Quick checklist

1. Obtain the player’s 17-digit decimal SteamID64, normally beginning with 7656.
2. Choose ownerid for auth level 2 or moderatorid for auth level 1.
3. Send the first grant through the server console, RCON, or the hosting-panel console.
4. Use the exact command syntax and keep the optional name and note in quotes.
5. Reconnect the player and test only the commands appropriate to the assigned level.
6. Inspect the active identity’s users.cfg.
7. If the entry is missing, run server.writecfg and check the file again.
8. For a departure or downgrade, run the matching removal command and verify that no unwanted grant remains.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.