Rust Server Admin Commands and Wipe Management

Running a Rust server is as much about administration as setup. Between moderating players, tuning the world and managing the all-important wipe cycle, you'll live in the console and RCON. Here are the commands and practices that matter.

Getting admin access

Add yourself as owner so you can run commands in-game and via RCON. From the server console (F1 in-game if you have access, or over RCON):

ownerid STEAMID64 "YourName" "server owner"
server.writecfg

ownerid grants full admin; moderatorid grants a reduced set for trusted staff. Always run server.writecfg to persist changes.

Essential moderation commands

The everyday toolkit for keeping a server civil:

kick "playername" "reason"
ban "playername" "reason"
banid STEAMID64 "name" "reason"
unban STEAMID64
say "message to everyone"

To see who's connected and their stats:

players
status

Useful server tuning commands

Adjust the world live without a restart:

env.time 12          # set time of day (12 = noon)
weather.clear        # clear the weather
airdrop.min_players 5 # players needed before airdrops spawn

For gather rates and other convars, most modded servers set these in config or via Oxide plugins rather than by hand.

RCON: administering without SSH

RCON lets you run all of the above from a desktop tool like RustAdmin or a web RCON client, connecting to your server's RCON port with the password you set at launch. It's the practical way to moderate during a busy session — you get a live console, player list and chat without touching the terminal. Never run RCON without a strong password; it grants total control.

The wipe: Rust's heartbeat

Rust servers wipe on a schedule — deleting the map (and often blueprints) to reset the economy and pull players back. Understanding wipe types is key to a healthy player base:

• Map wipe — new map, players keep learned blueprints. Lighter reset.
• Blueprint (BP) wipe — also resets learned blueprints, so everyone starts from scratch. Bigger reset, usually monthly.
• Full wipe — map plus blueprints together.

Most servers run a weekly map wipe with a monthly BP wipe, timed to Facepunch's monthly forced wipe (the first Thursday), when a Rust update wipes all servers anyway.

How to wipe

A wipe means clearing the save files for your server identity and generating a fresh map. The map regenerates from your server.seed and server.worldsize:

• Same map: keep the seed to regenerate an identical layout.
• Fresh map: change the seed (many owners randomise it) so the world is new.

Delete the map save and player/blueprint data as appropriate for the wipe type, then restart. Many admins script this to run automatically before the scheduled restart.

Announce and schedule wipes

Players plan their week around wipe day, so consistency builds a community:

• Pick a fixed wipe day and time and stick to it.
• Announce upcoming wipes in-game and on your Discord.
• Consider timers that broadcast "wipe in X hours" as it approaches.

A predictable wipe schedule is one of the biggest factors in whether players return week after week.

Oxide plugins for admin

If you run Oxide (uMod), plugins add far richer admin tools — GUI menus, automated wipe scheduling, kits, and detailed logs. They install over your server files and need updating after Rust patches.

Where hosting helps

Wipe day is your peak-load moment — everyone joins at once to claim the fresh map — so your server needs headroom exactly when it's busiest. Nxeon's fast-core NVMe VPS handles map generation and the wipe-day rush smoothly, and full root plus open RCON access mean you can script wipes, run Oxide and administer however you like. Set a consistent schedule, automate the wipe, and your Rust community will keep coming back.