Rust Server Setup Guide: Oxide, Plugins, Konfiguration

Setting up your own Rust dedicated server gives you full control over the rules, the map, the plugins, and who gets to play. Whether you want a chill PvE build server or a hardcore raiding arena, running your own box is the way to go.

This guide walks you through everything from installing the server to loading Oxide plugins and tweaking your configuration files.

Rust floating village monument with detailed structures

Requirements

Before you start, here is what you need:

A dedicated server or VPS with at least 8 GB RAM (16 GB recommended for larger maps)
A modern multi-core CPU - Rust is CPU-heavy
SSD storage with at least 10 GB free
A stable internet connection with decent upload speed
Windows or Linux operating system
SteamCMD installed

For most people, renting a Rust server from a hosting provider is the easiest path. You skip the hardware headaches and get started in minutes.

Self-hosting port forwarding: If you are running the server at home or on a VPS without a managed firewall, open these ports: TCP/UDP 28015 (game traffic) and UDP 28016 (RCON web). Without this, players cannot connect.

Step 1: Install SteamCMD and the Rust Server

SteamCMD is the command-line tool Valve provides for downloading dedicated server files. Grab it from the official Steam developer site.

Once SteamCMD is ready, run these commands:

App ID 258550 is the Rust dedicated server. The validate flag checks file integrity, useful after updates or if something breaks.

Step 2: Create Your Startup Script

Create a file called start.sh (Linux) or start.bat (Windows):

Key parameters explained:

server.worldsize - Map size in meters. 4000 is standard. Smaller maps (2000-3000) suit smaller groups and load faster.
server.seed - The random seed that generates your map. Change it for a different layout.
server.saveinterval - How often the server saves in seconds. 300 (5 minutes) is a solid default.
server.maxplayers - Most community servers run 50-200 players.
server.identity - A unique name for your server instance that controls where save files are stored. Set it once and never change it, or you will lose your world.

Step 3: Install Oxide (uMod)

Oxide is the most popular modding framework for Rust. Almost every plugin requires it. Here is how to install it:

Download the latest Oxide build from umod.org
Extract the files into your Rust server directory, overwriting existing files when prompted
Restart the server

After the restart, verify by typing oxide.version in the server console.

Rust beach landscape with palm trees and rocks

Step 4: Install Plugins

Plugins go into the oxide/plugins folder. Drop the .cs file in and the server compiles and loads it automatically. No restart needed for most plugins.

Essential Plugins for Any Server

GatherManager - Adjust resource gathering rates (2x, 3x, 5x, etc.)
NTeleportation - Let players set homes and teleport
Clans - Clan system with tags and shared doors
BetterChat - Custom chat formatting, colors, and group prefixes
RemoverTool - Allow players to remove misplaced building parts
AutoDoors - Doors close automatically after a set time
QuickSmelt - Speed up furnace smelting

Place plugins in: /server/rust/oxide/plugins/

The server auto-compiles and loads them. Check the console for errors if something does not work.

Step 5: Server Configuration

server.cfg

Your server.cfg file lives in server/rust/cfg/. This is where you set persistent server variables:

Oxide Configuration Files

Each plugin generates its own config file in oxide/config/. After a plugin loads for the first time, edit its JSON config to customize behavior. For example, GatherManager config:

After editing, use oxide.reload PluginName in the console to apply changes.

Rust ocean base with sails near oil rig

Step 6: RCON and Server Management

RCON (Remote Console) lets you manage the server without being in-game. Set it up in your launch script with +rcon.port and +rcon.password.

Popular RCON tools:

RustAdmin - Desktop app with a clean GUI, player list, and chat log
BattleMetrics - Web-based RCON with player tracking, ban lists, and scheduling
WebRCON - Browser-based console access at http://your-ip:28016

Common RCON commands:

Step 7: Wipe Schedule and Maintenance

Rust has a forced wipe on the first Thursday of every month when Facepunch pushes a major update. Most community servers also do a bi-weekly map wipe to keep things fresh.

Typical setup:

Map wipe - Every 2 weeks (weekly for high-pop servers)
Blueprint wipe - Monthly on forced wipe day, or less frequently

Performance Tips

Keep your plugin count reasonable. 30-40 well-maintained plugins is plenty. Going above 60 often causes lag.
Set fps.limit to 256 in your server config. Do not leave it uncapped.
Use an SSD. Rust server saves are frequent and large.
Monitor your RAM usage. A 4000-size map with 100+ players can use 10-12 GB of RAM.
Update Oxide and plugins regularly. Outdated plugins cause crashes and exploits.
Restart the server on a schedule (daily at 5 AM) to clear memory leaks. Use a cron job or Windows Task Scheduler.

Ready to Play?

Setting up a Rust server takes some effort, but once it is running, you have complete control over your experience. From custom gather rates to unique plugins, your server can be exactly what you want.

If you would rather skip the setup and jump straight into managing your community, check out DoomHosting Rust server hosting. One-click Oxide installation, automatic updates, and full RCON access included.