Rust server admin commands guide for owners
Facepunch Rust admin and F1 commands for server owners—auth levels, bans, kits, and wipe tools (not ranked third-party cheats).
Rust server admin commands are built into Facepunch’s dedicated and hosted servers. They help owners moderate players, spawn items for events, and debug plugins—not the same as private Rust cheats used on official Steam servers protected by Easy Anti-Cheat (EAC). This guide lists the F1 and RCON commands every owner should know, with safe workflows for wipes and support tickets.
Who can run admin commands
Only players with auth level 1 (moderator) or auth level 2 (admin) on that server can use admin commands from the F1 console. On your own local test server you are admin by default. On a rented host, grant auth through your panel or with ownerid and moderatorid in users.cfg after connecting once.
Commands typed in F1 without a slash affect only that server instance. They never work on Facepunch official servers unless you are on the developer test branch with explicit permissions—which normal players never receive.
Essential admin command reference
The table below covers moderation and utility commands operators use daily. Syntax may vary slightly by Oxide/uMod plugins; core Facepunch commands stay consistent across most wipes.
| Command | Effect | Notes |
|---|---|---|
| kick "name" "reason" | Disconnects a player | Use partial name match |
| ban "name" "reason" | Adds Steam ID to ban list | Pair with unban for appeals |
| unban SteamID64 | Removes ban entry | Verify ID in host logs |
| mute "name" | Blocks chat for player | Plugin servers may differ |
| teleport "name" | Moves target to your position | Use for stuck reports |
| teleport2me "name" | Alias on some hosts | Same as teleport |
| inventory.give "item" amount | Gives item to your inventory | Event servers only |
| spawn item "name" | Spawns entity at look position | Requires admin auth |
| global.say "message" | Broadcast to chat | Wipe announcements |
| server.writecfg | Saves config changes | After auth edits |
| status | Lists connected players | Copy Steam IDs for bans |
| quit | Shuts down server process | Use host restart instead in prod |
Auth setup with ownerid and moderatorid
After you join your server once, note your Steam64 ID from status or your host dashboard. Add ownerid "SteamID64" "YourName" to users.cfg for full admin, or moderatorid for kick-only staff. Run server.writecfg and restart so wipes do not wipe auth lines stored on disk.
F1 console vs chat commands
Most admin tools run in the F1 developer console with cheats enabled on the server. Chat commands like /kit may come from plugins. For a full console walkthrough, read how to use Rust admin commands and F1 console commands for admins.
Owner servers vs official EAC servers
Admin commands are legitimate on servers you control. On Facepunch official and most public Steam servers, third-party loaders are blocked by EAC—see our features guide for ESP, aimbot, and radar modules designed for that environment, not RCON kits.
GetRustCheats at getrustcheats.org maintains private Rust cheats for Steam PC official and modded servers—not server-owner admin commands on live wipe day. Modules ship through the operator portal with secure checkout, Discord support, and live status before Facepunch updates.
Easy Anti-Cheat (EAC) enforcement is real: read the status banner, reload the external loader after patches, and start with conservative ESP and aim settings. Humanized smoothing beats obvious snap aim in player reports and demo review.
Browse related guides on this blog—Lite vs Pro, features guide, EAC patch checklist, and how to buy. Start at Rust Cheats when you are ready to move beyond vanilla F1 tools.