Rust admin commands are server-console instructions for owners and moderators. The essential workflow is: run users to obtain a player’s Steam64ID, grant access with ownerid or moderatorid, reconnect, and then use the command group that matches the job—moderation, teleportation, player support, world control, entity management or diagnostics. Syntax and permissions can change with server builds, so confirm every command in Facepunch’s current command reference before using a copied list.
Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.
What Rust admin commands do
Rust’s dedicated-server console exposes commands that ordinary players cannot run. They let an authorized operator identify connected users, moderate disruptive behavior, move players for support or events, adjust the environment, inspect entities, save or restart the server, and diagnose performance. Commands can be entered in the server console, through a WebRCON client, or through a hosting control panel that forwards RCON commands.
| # | 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.
Authorization is separate from being the person who pays for a server. The server must recognize your Steam64ID at owner or moderator level, and the game client normally has to reconnect before the new level is active. A command copied from an old guide may be removed, renamed or restricted in a newer build; use find and the live Facepunch reference as your syntax check.
How to give yourself Rust admin access
1. Find your Steam64ID
At the server console, run:
usersThe command prints connected players and their Steam64IDs. Copy the complete numeric ID, not a display name. Names can contain spaces, change over time, or be duplicated; the ID is the reliable target for authorization and moderation.
#1 Best Overall
- 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*
2. Grant owner or moderator access
For full owner authorization, use:
ownerid <Steam64ID> "Name"For a lower-privilege moderator role, use:
moderatorid <Steam64ID> "Name"Replace the angle-bracketed value with the actual Steam64ID. Keep the quoted name accurate so the configuration remains understandable; the numeric ID is what matters for matching the account.
3. Reconnect before testing
Disconnect from the server and reconnect. Facepunch’s server guide explicitly notes that you need to reconnect after adding an account to obtain the authorization level. Testing without reconnecting is a common reason an apparently correct command returns a permission error.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Add an offline administrator in users.cfg
If the player is not online, edit the server identity’s configuration file:
rust/server/server.identity/cfg/users.cfgAdd the owner or moderator entry in the same format used by the server, keep Steam64IDs and names accurate, and restart or reload according to your host’s procedure. Make a backup before editing. A typo in an ID grants nobody access; an accidental change to the file can also prevent expected permissions after a restart.
Owner versus moderator permissions
| Role | How it is assigned | Practical use | Risk and control |
|---|---|---|---|
| Owner | ownerid <Steam64ID> "Name" |
Server administration, configuration, moderation and high-impact maintenance. | Largest blast radius. Limit this role to the actual operator and keep credentials private. |
| Moderator | moderatorid <Steam64ID> "Name" |
Day-to-day player support and moderation under the permissions allowed by the current build. | Safer for helpers, but still test what the role can execute before granting it on a live server. |
Exact command availability is build- and permission-sensitive. Use a test server or a low-impact command first, and remove access when a staff member no longer needs it.
Command discovery and server identity
| Command | What it is for | Useful practice |
|---|---|---|
users |
Lists connected players and Steam64IDs. | Run it before targeting a player by ID. |
find <term> |
Searches available commands and settings. | Use it when a copied command is missing or its spelling changed. |
version |
Reports the running server version. | Record it when troubleshooting a command that behaves differently from a guide. |
For example, find teleport can reveal which teleport variants the current build exposes. Treat the result as the authoritative spelling for that installation rather than assuming every historical command still exists.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRust moderation commands: kick, ban and mute
Immediate removal and bans
| Command | Typical purpose | Important check |
|---|---|---|
kick |
Removes a player from the server without necessarily imposing a lasting ban. | Confirm the correct player before executing; reconnecting may still be possible. |
ban |
Bans a player using the available name or player-target syntax. | Check the live reference for accepted arguments, reason and duration fields. |
banid |
Bans by Steam64ID. | Prefer the ID when names are ambiguous or the player is offline. |
banlistex |
Displays extended ban information where supported. | Use it to review stored reasons, dates or duration details. |
bans |
Lists current bans. | Review the list before adding or removing an entry. |
unban |
Removes a ban. | Use the same identifier format expected by the current build. |
Before a permanent action, verify the Steam64ID with users or the relevant ban-list output. Record a reason and, where the command supports it, a duration. A written moderation log makes appeals and staff handoffs easier than relying on memory.
Rank #2
Voice and chat controls
muterestricts a player’s voice or chat participation according to the server’s implementation.unmutereverses that restriction.
Test mute behavior with your current server version, because chat, voice and plugin systems can change which channel is affected.
Teleportation and observation commands
| Command | Use case | Operational caution |
|---|---|---|
teleport2me |
Brings a selected player to the administrator. | Warn the player first; teleporting into a dangerous location can cause immediate damage. |
teleport2marker |
Moves a player to the map marker location. | Check the marker and terrain before sending someone. |
teleportpos |
Teleports to specified coordinates. | Use verified coordinates and avoid placing players inside terrain or monuments. |
teleportany |
Provides a broader teleport target or destination workflow where supported. | Confirm the current syntax with find teleport. |
debug.lookingat |
Reports information about the entity or object under the crosshair. | Useful for identifying a building piece, deployable or player before an entity command. |
spectate |
Observes a player when enabled by the current build and authorization. | Check server rules and privacy expectations before using it for moderation. |
Use the least disruptive movement command that solves the problem. For a stranded player, bringing them to a safe administrator location is usually less destructive than guessing world coordinates.
Player assistance and testing
| Command | What it does | Safe use |
|---|---|---|
god true / god false |
Turns invulnerability on or off where authorized. | Explicitly switch it off after testing; otherwise combat or damage reports become misleading. |
noclip |
Enables a no-clip movement mode where supported. | Use for inspection, then disable it before returning to normal play. |
give |
Gives an item using the build’s accepted item and quantity syntax. | Check the live reference for arguments and avoid unintended economy changes. |
inventory.give |
Places an item in a player inventory where supported. | Target by the correct player and verify the resulting quantity. |
heal |
Restores player health where available. | Use for support or controlled tests, not as a substitute for diagnosing repeated damage. |
eat / drink |
Adjusts food or hydration where supported. | Confirm the command’s current target and amount syntax first. |
Commands that create items or alter survival statistics can affect progression and server economy. Keep a separate test identity or test server for demonstrations, and note every intervention on a live community server.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsWorld, weather and event controls
Time and weather
env.timesets or reports the in-game time using the syntax documented by the current build.env.progresstimecontrols whether time continues progressing where supported.weather.loadloads a weather state when available.
Weather controls and additional event or NPC commands vary more than basic identity and moderation commands. Run find weather, find event or find npc to see what the installed server exposes, then test on a staging instance. Changing time or weather during an event can affect visibility, farming, navigation and player expectations, so announce planned changes.
Entity and building operations
| Command | Purpose | How to avoid mistakes |
|---|---|---|
ent kill |
Removes the entity you are targeting. | Use debug.lookingat first and confirm the crosshair is on the intended object. |
ent lock |
Locks a targeted entity where supported. | Confirm ownership and explain the change to affected players. |
ent unlock |
Unlocks a targeted entity where supported. | Use only for a documented support or moderation reason. |
ent who |
Reports ownership or related entity information where available. | Capture the output before changing or deleting an object. |
Entity commands have a high accidental-damage risk because the target is often whatever the administrator is looking at. Move to a safe location, identify the entity, and execute one change at a time.
Saving, configuration and diagnostics
| Command | Role in operations | When to use it |
|---|---|---|
server.save |
Writes the current world state. | Before planned maintenance or a controlled restart. |
server.restart |
Restarts the server when supported. | Announce downtime and verify that players have time to log out safely. |
writecfg |
Writes current configuration values. | After deliberate changes that must persist, not as a blind fix for every issue. |
fps |
Reports performance information available to the server console. | Use for a quick symptom check, then compare across similar load periods. |
global.dump |
Produces diagnostic output where supported. | Capture output for troubleshooting and avoid running it repeatedly on a busy server. |
find |
Discovers current commands and variables. | First step when syntax or availability is uncertain. |
Profiling and diagnostic recording should be temporary. Facepunch warns that leaving the profiler enabled slightly reduces performance and that recording can degrade performance significantly. Start diagnostics, reproduce the issue, save the output, and disable recording rather than leaving it active during normal play.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Using WebRCON and RCON safely
RCON lets an administrator send server-console commands remotely instead of staying in the game. Facepunch’s server guide shows startup settings including:
Rank #3
- Acrylic Painting Pla Plastic
+rcon.port <port> +rcon.password <password> +rcon.web 1The exact port value is your configuration choice; do not confuse the RCON port with the game server or query port. A maintained WebRCON client or hosting panel can provide a browser interface, command history and access while you are offline from the game, but it also places a powerful credential on a network-facing service.
RCON security checklist
- Use a long, unique password and never paste it into public chat, screenshots or support tickets.
- Restrict inbound access with your host’s firewall, VPN or IP allow-list where practical.
- Expose only the RCON port required by your client; keep game and query ports configured separately.
- Give helpers individual accounts in the panel when available instead of sharing the owner credential.
- Review command history or audit logs after bans, item grants, wipes and configuration changes.
- Rotate the password when staff change or when you suspect it has leaked.
In-game console versus WebRCON
| Factor | In-game console | WebRCON or panel |
|---|---|---|
| Access location | Requires joining the server and having an authorized client. | Can be used remotely, including while offline from the game. |
| Auditability | Often limited to local or server-console output. | May provide command history and staff audit logs, depending on the client. |
| Credential exposure | Lower network exposure when used locally, but owner access still matters. | RCON password and port must be protected from network access and panel compromise. |
| Best fit | Quick support, live observation and commands tied to what you are looking at. | Scheduled maintenance, emergency moderation and administration away from the game. |
Self-hosted server versus rented hosting
| Factor | Self-hosted | Rented host |
|---|---|---|
| Hardware and network | You provide CPU, memory, storage, bandwidth, firewalling and uptime. | The provider supplies the machine and network; limits and policies vary by plan. |
| RCON setup | You configure startup flags, firewall rules and password storage. | A panel may expose WebRCON, but you still must secure credentials and ports. |
| Backups | You design, schedule and test backups. | Backup features depend on the host; verify retention and restoration before relying on them. |
| Automation | Full control over scripts, scheduled restarts and log collection. | Convenient automation may be available, with less control over the underlying system. |
| Geographic latency | Choose your own location and Internet provider. | Select an available data-center region close to your players. |
Neither model changes the command syntax. The difference is who is responsible for the operating system, network exposure, backups and recovery when a command or update causes trouble.
A safe command workflow for owners
- Identify the server and build. Run
versionand note the date of the maintenance window. - Identify the target. Run
usersand copy the Steam64ID; do not rely on a similar display name. - Discover syntax. Use
find <term>and check the current Facepunch reference for arguments and permission requirements. - Choose the least destructive action. Prefer
kickover a permanent ban when a temporary removal resolves the incident; use a safe teleport destination rather than unverified coordinates. - Announce and record. For restarts, weather changes, item grants and bans, record the reason, target, duration and operator.
- Save deliberately. Run
server.savebefore planned maintenance and usewritecfgonly after intentional configuration changes. - Verify the result. Recheck the ban list, player inventory, entity state or environment, and reconnect after authorization changes.
- Close diagnostic modes. Disable profiling, recording,
godandnoclipwhen testing ends.
Troubleshooting common failures
“Unknown command” or missing syntax
Run find <term>, check version, and compare the result with Facepunch’s live reference. A plugin command may also be absent after a plugin update or removal. Do not substitute a similarly named command without confirming its effect.
Permission denied after ownerid or moderatorid
Confirm the Steam64ID, verify that the command was entered on the intended server, and reconnect. If the entry was added to users.cfg, check its path and formatting, then restart or reload as required by the host.
Teleport or entity command affects the wrong target
Stop, identify the player by Steam64ID, and use debug.lookingat before entity operations. For coordinate teleports, verify the destination in a test session first; never assume a copied coordinate is safe on a different map seed.
RCON will not connect
Check that +rcon.port, +rcon.password and +rcon.web 1 are present in the startup configuration, that the client is using the RCON—not query—port, and that the firewall permits only the intended source. Rotate the password if it has been exposed.
Commands worth memorizing
usersfor Steam64IDs.owneridandmoderatoridfor authorization, followed by a reconnect.ban,banid,banlistex,bans,unban,kick,muteandunmutefor moderation.teleport2me,teleport2marker,teleportposanddebug.lookingatfor support and inspection.env.time,env.progresstimeandweather.loadfor environment control where enabled.ent kill,ent lock,ent unlockandent whofor targeted entity work.server.save,server.restart,writecfg,fps,global.dumpandfindfor operations.
The safest habit is not memorizing every argument. Memorize how to identify the target, discover the current syntax, make a backup or save, and verify the result.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
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.
