Rust Server Hosting Guide 2026: Setup and Optimization

Rust is one of the most demanding survival games to host, both in terms of hardware and administration. A populated Rust server needs fast CPUs, plenty of RAM, NVMe storage, and an admin who understands wipe cycles, plugin management, and performance tuning. This guide covers everything you need to run a Rust dedicated server in 2026: hardware sizing, Oxide/uMod plugin framework, wipe schedules, RCON configuration, map options, and the performance tweaks that keep your server running at a stable tick rate under real player load.

Hardware requirements

Rust is among the heaviest games to host. The server simulates AI, decay, crafting queues, player inventories, and the entire map in real time. Here is what you need:

RAM usage spikes during map generation and when many players are online simultaneously. A 4000-size map with 100 players easily consumes 12 GB of RAM. NVMe storage matters because Rust writes large save files (often 500 MB to 2 GB) on every server save, and slow disks cause noticeable freezes.

CPU clock speed is critical. Rust's core loop leans heavily on single-thread performance. Processors like the AMD Ryzen 9 7950X, with boost clocks above 5 GHz, provide the headroom needed to maintain a stable 30 tick rate under load.

Installing a Rust dedicated server

Facepunch distributes the Rust dedicated server through SteamCMD. The basic installation steps on Linux:

1. Install SteamCMD and its dependencies.
2. Download the server: steamcmd +login anonymous +force_install_dir /home/rust/server +app_update 258550 validate +quit.
3. Create a startup script with your server identity, map size, seed, and other parameters.
4. Launch: ./RustDedicated -batchmode +server.port 28015 +server.identity "myserver" +server.seed 12345 +server.worldsize 4000 +server.maxplayers 100.

On a managed game panel like the one at HostValues, you configure these parameters through the web interface. The panel handles SteamCMD updates, startup flags, and crash restarts automatically.

Oxide/uMod: the plugin framework

Oxide (also called uMod) is the standard plugin framework for Rust servers. It hooks into the server process and lets you load C# plugins that modify gameplay, add features, and automate administration. Virtually every community and modded Rust server runs Oxide.

Installation is straightforward: download the latest Oxide release, extract it over your server directory (it adds a few DLLs and creates an oxide folder), and restart. From there, install plugins by dropping .cs files into oxide/plugins. The server compiles them on load.

Essential plugins for most servers:

• Gather Manager: adjust resource gathering rates. Most modded servers run 2x to 5x gather.
• Teleportation: let players set homes and teleport. Popular on casual and PvE servers.
• Clans: team management beyond the built-in squad system.
• Better Chat: custom chat formatting, name colors, and group tags.
• Stack Size Controller: increase item stack sizes for convenience on modded servers.
• Anti-cheat helpers: while Rust has EAC (Easy Anti-Cheat), server-side plugins like Admin Radar and Spectate help admins investigate reports.

Keep your plugins updated. Facepunch pushes monthly Rust updates that sometimes break Oxide compatibility. Update the server, then update Oxide, then check each plugin. A staging server where you test updates before pushing them live saves your community from downtime.

Wipe schedules and planning

Rust has two types of wipes: map wipes and blueprint wipes. Understanding the rhythm is essential.

Forced wipes happen on the first Thursday of every month when Facepunch releases a major update. Every server wipes its map. You cannot avoid this.

Blueprint wipes reset all learned blueprints. Facepunch forces these a few times a year, but server owners can schedule additional BP wipes. Most community servers wipe blueprints monthly or biweekly to keep the progression loop fresh.

Custom map wipes are at the admin's discretion. Weekly wipe servers attract PvP-focused players who want fast progression. Biweekly or monthly servers suit builders and groups who invest time in large bases. Match your wipe schedule to your target audience.

Announce wipe schedules clearly on your server listing, Discord, and website. Nothing drives players away faster than surprise wipes. Consistency builds trust: if you say "biweekly Thursday 18:00 UTC," stick to it.

RCON: remote server management

RCON (Remote Console) lets you execute server commands without being in-game. Rust uses the WebSocket-based RCON protocol on port 28016 by default.

Enable RCON in your startup parameters:

+rcon.web 1 +rcon.port 28016 +rcon.password "YourSecurePassword"

Use a dedicated RCON client like RustAdmin, rcon.io, or a Discord bot that sends commands through RCON. Essential commands include server.save (force a save), kick, ban, server.writecfg (save config changes), and oxide.reload (reload a plugin without restarting).

Security matters. Set a strong RCON password, restrict the RCON port to trusted IPs in your firewall, and never expose it to the public internet without protection. A compromised RCON connection gives full server control to the attacker.

Map sizes and seeds

Rust maps are procedurally generated from a seed and size value. The server.worldsize parameter controls the map area. Common sizes:

• 3000: compact, suited for 25 to 50 players. Encourages early encounters and fast-paced gameplay.
• 3500: a balanced choice for 50 to 100 players. Enough space for base building without emptiness.
• 4000: the default and most popular. Works well for 75 to 150 players.
• 4500 to 6000: large maps for high-pop servers or servers focused on exploration. RAM usage increases significantly.

Preview seeds before committing. Tools like RustMaps.com let you visualize a seed and size combination, showing monument placement, biome distribution, and terrain layout. A good seed with well-distributed monuments keeps gameplay engaging across the entire map.

Performance optimization

Rust's target tick rate is 30. When it drops, players experience rubber-banding, delayed hit registration, and desync. Here is how to keep it stable:

• Right-size your map. A 6000-size map with 30 players wastes resources on empty terrain. Match map size to expected population.
• Limit entity count. Decaying bases, dropped items, and abandoned deployables accumulate. Use server.maxunloadedcleanupthreshold and decay settings to keep entities manageable.
• Tune garbage collection. Add +gc.buffer 2048 to your startup to give the .NET runtime more GC buffer, reducing stutter.
• Schedule automatic restarts. A daily restart during low-population hours clears memory leaks and accumulated state. Most game panels support scheduled tasks.
• Monitor with RCON tools. Track tick rate (perf command), entity count (ent count), and memory usage. Investigate when the tick rate drops below 25.
• Keep plugins lean. Each Oxide plugin runs in the server process. Poorly written plugins or plugins that run expensive logic on every tick are the most common cause of performance problems after hardware limits.

NVMe storage directly impacts save performance. Rust writes its save file every 300 to 600 seconds by default. On a spinning disk, a 1 GB save file causes a multi-second freeze. On NVMe, it completes in the background without players noticing.

Server security and anti-cheat

Rust uses EAC (Easy Anti-Cheat) on the client side, which catches most basic cheats. Server-side, you need additional layers:

• Set a strong RCON password and restrict the port to trusted IPs.
• Run server update checks regularly. Facepunch patches exploits alongside monthly updates.
• Use admin tools like Spectate and Admin Radar plugins to investigate player reports.
• Set up Discord webhooks for alerts: player connects, disconnects, chat logs, and ban notifications give you real-time visibility.

DDoS attacks are common against popular Rust servers, especially after controversial bans or during competitive events. Hosting with a provider that includes network-level DDoS mitigation, like HostValues, means attacks are absorbed before they reach your server process.

Frequently asked questions

How often should I wipe my Rust server?

It depends on your community. Weekly wipes suit PvP-focused players who want fast action. Biweekly wipes balance progression and conflict. Monthly wipes work for builders and role-players. Whatever you choose, announce the schedule clearly and stick to it. Forced wipes happen on the first Thursday of each month regardless of your custom schedule.

Can I run a Rust server on 8 GB of RAM?

Yes, for a small vanilla server with up to 50 players on a 3000 to 3500 size map. Once you add Oxide plugins and increase the map size or player count, expect to need 12 to 16 GB or more. Monitor actual usage after your first wipe and scale accordingly.

Do players need to install Oxide to join my modded server?

No. Oxide runs entirely server-side. Players connect with the standard Rust client. Some plugins may recommend client-side mods for extra features, but these are optional and not required to play.