How to Make a Rust Dedicated Server (2026 Guide)

Rust is the hardcore multiplayer survival game from Facepunch Studios — the one where you wake up naked on a procedurally generated island, harvest resources, build a base, and defend it from other players who want to raid you. Running your own Rust dedicated server gives you full control over slots, the wipe schedule, Oxide/uMod plugins and game rules. This guide covers both routes: self-hosting the server yourself with SteamCMD, and deploying a managed Rust server on the Flux decentralized cloud in about 30 seconds.

Before you start: what a Rust server actually needs

A Rust server is a CPU- and RAM-hungry piece of software. The map is generated in memory on boot, and every tree, building and player is simulated on the host. As a rule of thumb you want a modern high-clock CPU, 8 GB of RAM for a small community, and 10–12 GB once you push toward 100–200 players or a large map. You also need three open ports: 28015/UDP for game traffic, 28016/TCP for RCON, and 28017/TCP for the Steam query port that lists your server in the in-game browser.

Option A — Self-host a Rust server with SteamCMD

SteamCMD is Valve's command-line tool for downloading dedicated server files. The Rust dedicated server is Steam app 258550. On a Linux box (Debian/Ubuntu are the common choice) the flow looks like this:

  1. Install dependencies and a non-root user. Rust servers should never run as root. Create a dedicated rustserver user and install lib32gcc-s1, curl and tar.
  2. Download SteamCMD and run it. Point it at your install directory and run app_update 258550 validate to pull the latest Facepunch build. The download is several gigabytes and takes a few minutes.
  3. Create a launch script. Start RustDedicated with flags such as -batchmode +server.hostname "My Rust Server" +server.maxplayers 100 +server.worldsize 4000 +server.seed 12345 +rcon.password "yourpassword". The world size and seed control your procedural map; the max players sets your slot count.
  4. Open your firewall. Forward 28015/UDP, 28016/TCP and 28017/TCP. Without 28017 your server will run but never appear in the community server list.
  5. Keep it updated. Facepunch ships a mandatory patch on the first Thursday of every month (the forced wipe). When the client updates, your server must re-run the SteamCMD app_update or players cannot connect. Most admins wrap the server in a systemd service or a tool like LinuxGSM to automate restarts and updates.

Self-hosting is free if you already own the hardware, but it means you personally own patching, DDoS mitigation, backups, uptime and the monthly wipe update at midnight. That is a real time commitment on a game that patches every month.

Option B — Deploy a managed Rust server on Flux in ~30 seconds

If you would rather skip the sysadmin work, a managed host provisions all of the above for you. On Rust on Flux you create an account, pick a plan sized to your community (8 GB for ~50 slots, 10 GB for ~100, 12 GB for ~200), choose Vanilla or Oxide/uMod, pick a region close to your players, and click deploy. The server is live in under 30 seconds with the correct ports already open, DDoS protection on, and a web dashboard for the console, file manager and backups. Because Flux is a decentralized cloud spread across 50+ countries and thousands of independent nodes, there is no single point of failure.

Installing Oxide / uMod on your Rust server

Oxide (now maintained as uMod) is the modding framework that powers the vast majority of community Rust servers — kits, teleportation, economy, events, admin tools and thousands of other plugins. To mod a self-hosted server you download the Oxide build for Rust, extract it over your server files, restart, and drop .cs plugin files into the oxide/plugins folder where they hot-load. On Flux you simply choose the Modded (Oxide) edition at deploy time and the framework is already installed — then manage plugins from the dashboard file browser.

Connecting to your new Rust server

Once the server is live, press F1 in Rust to open the console and type client.connect yourserverip:28015, or find it in the Community tab of the server browser (this needs the 28017 query port open). Share the IP and port with your friends and you are ready to wipe, build and raid.

Setup guide FAQ

What Steam app ID is the Rust dedicated server?

The Rust dedicated server is Steam app 258550. You install it with SteamCMD using app_update 258550 validate. (The Rust game client itself is app 252490.)

How much RAM do I need to host a Rust server?

Around 8 GB for a small server, and 10–12 GB for 100–200 players or a large map. Rust's RAM use scales with map size and player count because the whole world is simulated in memory.

Do I have to update my server every month?

Yes. Facepunch forces a wipe with a mandatory patch on the first Thursday of each month. Self-hosters must re-run the SteamCMD update; managed hosts like Flux handle it automatically.

Is it hard to host a Rust server myself?

Self-hosting with SteamCMD is very doable but ongoing: you own updates, ports, backups and DDoS protection. A managed deploy removes that maintenance so you can focus on running your community.

Ready to skip the setup? Deploy a Rust dedicated server on Flux in under 30 seconds — Vanilla or Oxide, first month free.

Related Rust hosting guides