How to Host a Rust Server: Complete Guide

Rust is one of the most demanding games to host. Before you spin up a server, it helps to understand what the game actually needs from the hardware, how the modding ecosystem works, and what ongoing maintenance looks like.

What Rust needs from a server

A busy 100-player server typically needs 16 GB RAM or more and a fast CPU. Smaller community servers running 25 to 50 players can work on 8 GB, but RAM headroom matters - Rust's world simulation is memory-intensive and usage grows with player count and world activity.

Storage fills up quickly. Rust world files are large, and if you keep save backups before wipes (which you should), plan for at least 20 to 30 GB of dedicated server storage. A fast SSD makes a noticeable difference to world save times.

Vanilla vs modded

A vanilla server runs the official Facepunch dedicated server with no third-party framework. It behaves identically to official Facepunch servers and attracts players who want the base game experience with no extras.

Modded means running the Oxide (uMod) framework on top of the dedicated server. Oxide adds a plugin layer that lets you extend and customise the game without touching the server binary. The vast majority of community servers run Oxide because it unlocks quality-of-life features, economy systems, and admin tools that vanilla does not have.

Installing Oxide (uMod)

Oxide installs on top of an existing Rust dedicated server installation. The process is straightforward:

1. Install the Rust Dedicated Server via SteamCMD (app ID 258550).
2. Download the Oxide build for Rust from umod.org.
3. Extract the Oxide files into your server directory - they overlay the existing installation.
4. Start the server. Oxide initialises on first run and creates the /oxide/ directory structure.

Plugins are .cs files (C#) compiled by Oxide at runtime. To install a plugin, drop its .cs file into /oxide/plugins/ and it loads automatically - no restart required in most cases.

Popular community plugins include Clans (group system), Economics (in-game currency), NTeleportation (player teleport commands), and SignArtist (custom images on in-game signs). All are available on umod.org.

Wipe schedules

Rust forces a map wipe whenever Facepunch pushes a forced update - this happens on the first Thursday of each month. The wipe deletes all player progress and map data, and everyone starts fresh. As a server owner you cannot skip forced wipes.

You can also run your own scheduled wipes independently of Facepunch updates. Many community servers wipe weekly or bi-weekly to keep the map fresh and the population active.

Before any wipe, run an automated backup of your server data - player data, oxide data, and map files. This lets you restore if something goes wrong during the wipe process. Set this up as a scheduled task on the server, not something you do manually.

Blueprint wipes (resetting crafting progression) are separate from map wipes. You can wipe the map without wiping blueprints, which many communities prefer for mid-cycle wipes.

RCON

Rust uses RCON (Remote Console) for admin access. You set the relevant options in your server startup arguments or server.cfg:

• +rcon.password "yourpassword"
• +rcon.port 28016
• +rcon.web 1 (enables WebRCON support)

You can manage the server via browser-based tools like WebRCON or desktop RCON clients. RCON gives you access to admin commands, player management, and live console output without needing SSH access to the machine.

Key server.cfg settings

Your server.cfg controls the core server identity and behaviour. The most important settings:

• server.hostname - the name that appears in the server browser
• server.maxplayers - maximum concurrent player count
• server.worldsize - map size in metres (default 4000; smaller maps mean denser player interaction)
• server.seed - the procedural generation seed; if not set, a random seed is used on each wipe
• server.description - description shown in the server browser

Set a fixed server.seed if you want the same map layout each wipe cycle. Use a new seed each wipe if you want map variety.

Hosting Rust on Zeros Host

Zeros Host offers Rust hosting with one-click Oxide installation, RCON access built into the panel, and automated wipe scheduling so you do not have to manage wipe scripts manually. Servers run on UK and EU nodes. See the pricing page for current plan details.