Running your own Rust server means you decide the map, the rules, the wipe schedule and the plugins. It also means you need to understand a handful of settings that every Rust admin runs into sooner or later: the seed and world size, the identity folder, RCON, and the monthly forced wipe. This guide walks through each of them so your first server starts cleanly and stays easy to manage.
What you need before you start
- A server with enough RAM. Rust is one of the most memory-hungry survival games. Map size, player count and plugins all add to it (see the RAM table below).
- A fast CPU. Rust's server simulation runs mostly on one main thread, so high single-core speed matters more than core count.
- The Rust Dedicated Server. It is a free download through SteamCMD (app ID
258550). You do not need to own the game on the server account. - Open ports. By default Rust uses
28015UDP for game traffic,28016TCP for RCON and28017UDP for the server query (server browser). The Rust+ companion app uses28082TCP.
If you install it yourself on Linux, the download looks like this:
steamcmd +force_install_dir /home/rust/server +login anonymous +app_update 258550 validate +quitOn managed game server hosting the install and updates are done for you, and you change the same settings through the control panel's startup options and config files instead.
The basic launch command
Rust is configured mostly through launch parameters. A typical start command for a vanilla server looks like this:
./RustDedicated -batchmode -nographics \
+server.port 28015 \
+server.queryport 28017 \
+server.level "Procedural Map" \
+server.seed 1234567 \
+server.worldsize 3500 \
+server.maxplayers 100 \
+server.hostname "My Rust Server | Monthly Wipe" \
+server.description "Vanilla, monthly wipe, active admins" \
+server.identity "main" \
+rcon.web 1 \
+rcon.port 28016 \
+rcon.password "use-a-long-random-password"Here are the settings that matter most.
server.seed
The seed is a number that the procedural map generator uses to build the terrain, monuments, rivers and roads. The same seed and world size always produce the same map, which is why players share seeds. Any value from 0 to 2147483647 works. Before you commit to one, preview it on a map site such as RustMaps so you know which monuments it has and whether the layout suits your player count.
server.worldsize
World size is the length of one side of the map in metres, from 1000 to 6000. A bigger map gives players more room but costs more RAM, takes longer to generate and can feel empty with a small population. As a rule of thumb:
- 1000 - 2500: small groups, creative or arena servers, and testing.
- 3000 - 3500: the sweet spot for most community servers with up to around 100 players.
- 4000 - 4500: busy servers with 150 or more players, similar to official servers.
- 5000+: rarely worth it unless you have a very large population.
server.maxplayers
This sets the player slot limit. Be realistic: an empty 200-slot server looks dead in the browser, while a full 50-slot server attracts more players. Match it to the map size and to the resources you have.
server.identity
The identity is the name of the folder where the server stores everything about this world: the map, the save file, player data, blueprints and your cfg files. With +server.identity "main" those live in server/main/. Keep the identity the same between restarts, or the server will start a brand new world in a new folder. You can also use different identities to keep several worlds side by side and switch between them.
Inside the identity folder, cfg/server.cfg is a convenient place for convars you want applied on every start, and cfg/users.cfg stores owners and moderators:
ownerid 76561198000000000 "YourName" "Server owner"
moderatorid 76561198000000001 "Helper" "Moderator"You can also add them from the console with ownerid or moderatorid, followed by server.writecfg to save.
Setting up RCON
RCON (remote console) lets you run server commands without being in the game: kick and ban players, broadcast messages, save the world or check performance. With +rcon.web 1 the server uses the WebSocket RCON protocol, which works with tools such as RustAdmin and other web-based consoles.
- Use a long random password. Anyone with it has full control of your server.
- Do not reuse a password from anywhere else, and change it if a former admin leaves.
- Only open the RCON port if you actually connect from outside. If your host's panel already gives you a live console, you may not need external RCON at all.
Some useful commands, whether you run them over RCON or in the panel console:
| Command | What it does |
|---|---|
save | Saves the world immediately |
status | Lists connected players and their Steam IDs |
say "message" | Broadcasts a chat message |
kick <name or id> "reason" | Kicks a player |
banid <steamid> "name" "reason" | Bans a player by Steam ID |
server.writecfg | Writes the current settings and user list to the cfg files |
quit | Saves and shuts the server down cleanly |
Understanding wipes
Wipes are part of what makes Rust what it is. A wipe resets progress so everyone starts on equal terms again. There are two kinds, and it is important to know the difference.
Map wipes
A map wipe removes the world: every building, deployable and item on the map. Players keep the blueprints they have learned. To map wipe, stop the server and delete the map and save files from your identity folder. They are named after the world size, seed and save version, for example:
server/main/proceduralmap.3500.1234567.<version>.map
server/main/proceduralmap.3500.1234567.<version>.savMany admins also change the seed on each map wipe so players get a fresh layout to explore.
Blueprint wipes
A blueprint wipe resets what each player has learned, so everyone has to research and craft their way back up. To do one, stop the server and delete the blueprint database files in the identity folder, named like player.blueprints.<version>.db (plus any matching -wal or -journal files). Most servers combine a blueprint wipe with a map wipe on a fixed schedule, such as every forced wipe or every other month.
The monthly forced wipe
Facepunch releases a major update on the first Thursday of every month, usually around 19:00 UK time. That update changes the save format, so every server has to map wipe whether it wants to or not: old map saves will not load on the new version. Blueprints are not reset by every forced wipe, so check the patch notes each month.
Plan for it:
- Announce the wipe time on Discord and in the server description a few days ahead.
- Back up your identity folder, especially
cfgand any plugin data you want to keep. - Update the server once the patch is live, and update Oxide or Carbon at the same time (see below).
- Pick a new seed if you want one, then start the server and check the console for errors.
Many servers also do weekly or twice-weekly map wipes between forced wipes. That is your choice, and it is a big part of what kind of community you attract.
Plugins: Oxide (uMod) and Carbon
Vanilla Rust is fine for many players, but most community servers use plugins for things like kits, teleports, better loot, clans and admin tools. Rust has two main plugin frameworks:
| Oxide (uMod) | Carbon | |
|---|---|---|
| Maturity | The long-standing standard | Newer, actively developed |
| Plugin language | C# | C#, runs most Oxide plugins unchanged |
| Plugin folder | oxide/plugins | carbon/plugins |
| Config folder | oxide/config | carbon/configs |
| Focus | Compatibility and a huge plugin library | Performance and built-in admin tools |
A few rules that save a lot of trouble:
- Use one framework, not both. Installing Oxide and Carbon together will break the server.
- Update the framework with every Rust update. After the monthly patch, plugins will not load until Oxide or Carbon releases a matching build, which usually happens within hours.
- Add plugins one at a time. Drop the
.csfile in the plugins folder and it compiles and loads automatically. If something breaks, you know which plugin caused it. - Set permissions. Most plugins use permissions you grant with commands such as
oxide.grant group default kits.use(Carbon accepts the same commands).
Plugins add to CPU and RAM use, and a badly written one can drag down the whole server. Fewer, well-maintained plugins beat a long list of abandoned ones.
How much RAM does a Rust server need?
Memory use grows with map size, the number of entities players build, the number of players online and the plugins you run. It also creeps up over a wipe as bases get bigger. These figures are a realistic starting point:
| World size | Typical players | Suggested RAM |
|---|---|---|
| 1000 - 2500 | Up to 25 | 6 - 8 GB |
| 3000 - 3500 | 25 - 100 | 8 - 12 GB |
| 4000 - 4500 | 100 - 200 | 12 - 16 GB |
| 5000 - 6000 | 200+ | 16 GB or more |
Add a few gigabytes on top if you run a large plugin set, and expect usage to be highest near the end of a wipe. If the server starts lagging late in a wipe, a scheduled restart every day or two clears memory and keeps performance steady.
A quick checklist for launch day
- Seed previewed and world size chosen to suit your expected player count.
- A fixed
server.identityso restarts keep the same world. - Hostname, description, header image and URL set so the server looks good in the browser.
- Owner and moderators added to
users.cfg. - A strong RCON password, or no external RCON at all.
- Wipe schedule decided and announced, with the forced wipe on the first Thursday in your calendar.
- Oxide or Carbon installed (not both), with a short, tested list of plugins.
- Enough RAM for your map size, with headroom for the end of the wipe.
Get these right and your server will be stable from day one. After that, the hard part is building a community, and the best way to do that is to wipe on time, stay active as an admin and keep the rules clear.