How to Set Up a Rust Dedicated Server

Running your own Rust dedicated server gives you full control over wipe schedules, plugins, player limits, and gameplay rules. This guide covers everything you need to know to get a Rust server running, whether you self-host or use a managed provider.

Hardware Requirements

Rust is a demanding game on both the client and server side. At a minimum, your dedicated server needs:

• CPU: A modern multi-core processor (4+ cores recommended). Rust server performance is largely single-threaded, so clock speed matters more than core count.
• RAM: 8 GB minimum for a small server (up to 50 players on a 3000-size map). Budget 12-16 GB for larger maps or 100+ player servers.
• Storage: 10-15 GB for the base server files, plus additional space for world saves and oxide/plugin data. An SSD is strongly recommended for faster world loading.
• Network: A stable connection with low latency and at least 10 Mbps upload. Rust servers generate significant network traffic during peak activity.

Port Configuration

Rust uses four ports. All must be open in your firewall and forwarded through your router if hosting at home.

Port	Protocol	Purpose
28015	UDP	Game server (player connections)
28016	TCP	RCON (remote console administration)
27015	UDP	Steam query (server browser listing)
28017	TCP	Web RCON (optional, for web-based panels)

If you run multiple Rust server instances on one machine, space each instance at least 10 ports apart to avoid conflicts.

Installation with SteamCMD

SteamCMD is Valve's command-line tool for downloading dedicated server files. It does not require a Steam login for Rust.

Step 1: Install SteamCMD

On Linux (Ubuntu/Debian):

sudo add-apt-repository multiverse
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install steamcmd

On Windows, download the SteamCMD installer from the Valve Developer Community wiki and extract it to a directory like C:\steamcmd.

Step 2: Download the Rust Server

Run SteamCMD and execute:

login anonymous
force_install_dir /home/rustserver/rust_server
app_update 258550 validate
quit

App ID 258550 is the Rust Dedicated Server. The validate flag ensures all files are verified.

Step 3: Configure Your Server

Create a startup script with your desired settings:

./RustDedicated -batchmode \
  +server.ip 0.0.0.0 \
  +server.port 28015 \
  +server.tickrate 30 \
  +server.hostname "My Rust Server" \
  +server.identity "my_server" \
  +server.seed 12345 \
  +server.maxplayers 100 \
  +server.worldsize 4000 \
  +server.saveinterval 600 \
  +rcon.ip 0.0.0.0 \
  +rcon.port 28016 \
  +rcon.password "YourSecurePassword" \
  +rcon.web 1

Key Parameters Explained

• server.tickrate: Controls server simulation rate. 30 is standard; higher values use more CPU.
• server.seed: Determines the procedural map generation. Change it each wipe for a fresh map.
• server.worldsize: Map size in meters. 3000-4000 is typical for 50-100 player servers.
• server.saveinterval: How often the world saves to disk, in seconds. 600 (10 minutes) balances safety and performance.

Keeping Your Server Updated

Rust updates on the first Thursday of every month. Your server must match the client version or players cannot connect. Automate updates by running SteamCMD with app_update 258550 before each server start, or use a cron job.

Installing Oxide/uMod for Plugins

Most community Rust servers use the Oxide (uMod) framework for plugins. Download the latest Oxide build from umod.org, extract it into your server's root directory, and restart. Plugins go in the oxide/plugins folder and load automatically. See the best Rust server plugins guide for recommended plugins.

Security Best Practices

• RCON password: Always set a strong, unique RCON password. Never leave it blank or use defaults.
• Firewall: Only expose the ports listed above. Restrict RCON access to your own IP address.
• Backups: Automate regular backups of your server/{identity}/ directory, especially before monthly updates.
• Anti-cheat: Rust uses EasyAntiCheat by default. Supplement with server-side plugins like Rust:IO or admin tools.

Wipe Schedule Configuration

Understanding Rust wipe schedules is essential for any server operator. Configure your wipe cadence in the server description so players know what to expect, and plan your forced wipes around Facepunch's monthly update cycle.

Next Steps

Once your server is running, consider customizing the experience with plugins and mods, setting up a Discord webhook for server events, and establishing clear server rules. A well-configured Rust server with an active admin team is what keeps players coming back wipe after wipe.