How to Set Up a Rust Server From Scratch (2026 Guide)

Setting up a Rust server from scratch looks intimidating because of how many config files and command-line flags are involved, but the actual setup is a short, linear checklist once you know what each piece does. This guide covers a real dedicated Rust server setup — SteamCMD install, server.cfg, essential startup flags, and the wipe/oxide basics you need before opening it to players.

What You Need Before Starting

Rust is genuinely one of the heavier games to self-host. Minimum realistic specs for a small server (10-20 players) are a 4-core CPU with strong single-thread performance, 8-12GB RAM, and an SSD — Rust’s procedural map generation and constant entity saving punish slow storage badly. For 50+ players, budget 16GB+ RAM and a higher-clock CPU; Rust scales with player count far more aggressively than Minecraft does.

Step 1: Install SteamCMD

Rust dedicated servers are distributed through Steam’s server tool, SteamCMD, not a direct download. On a Linux VPS:

mkdir ~/steamcmd && cd ~/steamcmd
wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz
tar -xvzf steamcmd_linux.tar.gz
./steamcmd.sh

Once SteamCMD opens, log in anonymously (no Steam account needed for the server files) and install the Rust dedicated server app (App ID 258550):

login anonymous
force_install_dir ../rustserver
app_update 258550 validate
quit

This downloads several GB of server files — expect this step to take a while depending on your host’s connection speed.

Step 2: Build Your Startup Command

Rust servers launch via a command with flags, not a config file that’s read on its own — this trips up a lot of first-time hosts. A solid baseline startup command looks like this:

./RustDedicated -batchmode +server.port 28015 +server.identity "myserver" +rcon.port 28016 +rcon.password "changeme" +rcon.web true +server.hostname "My Rust Server" +server.level "Procedural Map" +server.seed 12345 +server.worldsize 4000 +server.maxplayers 100 +server.saveinterval 300

The flags that matter most for new hosts:

• server.worldsize — directly affects both RAM usage and how long map generation takes on first boot. 3000-3500 is reasonable for under 50 players; 4000-4500 for larger populations. Going above 4500 dramatically increases load time and resource use.
• server.seed — locks in your map layout. Change this and the entire map regenerates — useful to know before your first wipe, since keeping the same seed keeps the same map.
• rcon.password — never leave this as the example value; RCON gives full admin control, and a default or weak password is a common way servers get griefed or wiped by outsiders.
• server.saveinterval — how often (in seconds) the server auto-saves. 300 (5 minutes) is a safe default; lower it if your host is unstable, raise it slightly on very large maps to reduce save-related stutter.

Step 3: Open the Right Ports

Rust needs both the game port and the port immediately after it (used for Steam queries) open, plus your RCON port if you’re using it:

• 28015 UDP + TCP — main game port
• 28016 TCP — Steam query port (game port + 1)
• Your rcon.port — for remote console access and most web-based admin panels

Most managed game hosts open these automatically; on a raw VPS you’ll need to configure this in your firewall (ufw, iptables) or cloud provider’s security group settings.

Step 4: Install Oxide/uMod for Plugin Support

Vanilla Rust has no in-game admin tools beyond basic RCON commands — no kits, no teleport, no economy. Oxide (also called uMod) is the plugin framework almost every populated Rust server runs on. Installation is a matter of downloading the Oxide build matching your server’s branch and extracting it into your server’s root directory, overwriting the matching files. Restart the server afterward — a successful install shows Oxide’s version info in the console log on boot.

Once installed, plugins go in oxide/plugins/ as .cs files, and most are one-file drops with no further configuration needed beyond editing the auto-generated config file the plugin creates on first load.

Step 5: Understand Wipe Cycles Before Your First One

Rust’s meta revolves around wipes — resetting the map and, optionally, player blueprints/progress. Most populated servers follow a schedule (commonly monthly for map+blueprint wipes, with an additional mid-month map-only wipe). Decide your cycle before launch and announce it clearly; player retention on Rust servers depends heavily on wipe schedule predictability. To force a full wipe, delete the save files matching your server.identity folder and restart with a new server.seed if you also want a new map layout.

Frequently Asked Questions

How much RAM does a Rust server actually need?

8GB is a workable minimum for a small server under 20 players with a modest world size. Realistically, budget 12-16GB for 50+ players, and 16GB+ for a larger world size with a full modded/Oxide plugin stack — Rust’s memory usage climbs with both player count and world size independently.

Do I need Oxide to run a Rust server?

No — vanilla Rust runs fine without it. But nearly every populated public server uses Oxide for basic quality-of-life features (kits, teleport, chat commands, anti-cheat plugins), so most server owners install it before opening to the public.

What’s a safe first wipe schedule for a new server?

Monthly full wipes (map + blueprints) aligned with Rust’s official monthly force-wipe (the first Thursday of each month) is the most common and predictable schedule for new servers, since players already expect it from the wider Rust community.

Conclusion

A working Rust server comes down to five things: install via SteamCMD, build a startup command with the flags that actually matter (worldsize, seed, rcon password, save interval), open the right ports, install Oxide for admin tools, and decide your wipe schedule before you announce the server publicly. Get those five right and everything else is tuning, not troubleshooting.