Rust rewards a server with a clear identity: the right map size, a sensible wipe schedule, and a few quality-of-life plugins. This guide gets you from nothing to a running server you can grow.
Prefer a one-click start with mods ready to go? A Vastrox Rust plan installs the server and uMod for you.
Requirements
- A Linux or Windows machine with a strong single-core CPU (Rust is very CPU-bound)
- 8 GB RAM minimum, 16 GB for larger maps and player counts
- SteamCMD
- Ports open: 28015/UDP (game) and 28016/TCP (RCON)
Step 1: Install with SteamCMD
The Rust dedicated server app ID is 258550:
steamcmd +login anonymous +app_update 258550 validate +quit
Step 2: Create a start script
Rust launches with a long list of flags. A typical Linux start.sh:
./RustDedicated -batchmode \
+server.hostname "Your Server Name" \
+server.maxplayers 100 \
+server.worldsize 3500 \
+server.seed 12345 \
+server.saveinterval 300 \
+rcon.password "change-this" \
+rcon.port 28016
worldsize (1000 to 6000) and seed define the map. Keep the same seed and size between wipes if you want the same map.
Step 3: Plan your wipes
Rust expects regular wipes. Most servers do a map wipe weekly and a full wipe (including blueprints) on the first Thursday of the month, which lines up with Facepunch's forced wipe. Announce your schedule clearly, because players pick servers partly on wipe day.
Step 4: Add plugins with uMod (Oxide)
uMod is the standard plugin framework. Install it over your server files, restart, then drop plugin .cs files into oxide/plugins. Popular starters:
- Kits and Remover Tool for quality of life
- Clans for group play
- Server Rewards or a shop for retention
Step 5: Connect
In Rust, open the console with F1 and run:
client.connect your-ip:28015
Add it to favorites in the in-game browser so it is one click next time.
Performance notes
Rust performance is dominated by a single CPU core and by entity count. Smaller maps, sensible building limits and periodic restarts keep frame times low. See How to fix game server lag for tuning.
FAQ
How big should my Rust map be?
3000 to 3500 worldsize suits most community servers. Go larger only if you regularly fill the map.
How often should I wipe?
Weekly map wipes with a monthly full wipe is the common, expected pattern.
Why is my server not in the browser?
Give it a few minutes after first boot, confirm UDP 28015 is open, and make sure the map has finished generating.
Skip the setup and launch a Rust server with mods ready out of the box.