Rust, the open-world survival game from Facepunch Studios, demands serious hardware to run smoothly. With its procedurally generated maps, persistent building mechanics, and up to 500 players per server in 2026, running a dedicated server for Rust game hosting requires careful hardware planning. This guide covers everything from CPU selection to network configuration for hosting Rust in 2026.
If you already know your target player count, compare dedicated server plans on our comparison page to find a machine that meets these specifications.
Why Rust Needs Bare-Metal Dedicated Hardware
Rust’s server architecture is unique among survival games. It maintains a fully persistent, player-modified world where every structure, loot container, and deployable item must be tracked and synchronized. The server runs a single continuous simulation tick loop that processes all players, entities, and world interactions. Unlike games with zone-based instancing, Rust cannot distribute its load across multiple server processes — everything runs on one machine.
This monolithic architecture means that single-threaded CPU performance is the single most important factor for Rust server performance. A server with 64 slower cores will perform worse than one with 8 fast cores when hosting Rust.
Rust Dedicated Server Hardware Requirements 2026
CPU: Clock Speed Is Everything
Rust’s main simulation is bound to a single thread. The CPU must process all entity updates, building decay checks, animal AI, and player interactions within each tick (typically 10-15 ms per tick for a healthy server). If the tick rate drops below 10 FPS (100 ms per tick), players will experience rubberbanding and desync.
| Player Capacity | Minimum CPU | Recommended CPU | Expected Tick Rate |
|---|---|---|---|
| 50-100 players | 4 cores @ 3.5 GHz | 6 cores @ 4.5 GHz (Ryzen 5 7600X) | 15-20 FPS |
| 100-200 players | 6 cores @ 4.0 GHz | 8 cores @ 5.0 GHz (Ryzen 7 7800X3D) | 10-15 FPS |
| 200-350 players | 8 cores @ 4.5 GHz | 12 cores @ 5.3 GHz (Ryzen 9 7950X) | 8-12 FPS |
| 350-500 players | 12 cores @ 5.0 GHz | 16+ cores @ 5.5+ GHz (EPYC 4484PX / Threadripper) | 5-10 FPS |
Note that Rust servers at 350+ players almost always operate below 10 FPS tick rate even on the best hardware. This is a game engine limitation, not a hosting problem. Most Rust server operators cap populations at 200-300 players for optimal gameplay.
RAM: Oxide/Modded vs Vanilla
Rust RAM usage depends heavily on whether you run vanilla or modded (Oxide/uMod) servers:
| Server Type | Minimum RAM | Recommended RAM | Notes |
|---|---|---|---|
| Vanilla, 50-100 players | 8 GB | 12 GB | Clean install, no plugins |
| Vanilla, 100-200 players | 12 GB | 16 GB | More entities = more RAM |
| Modded/Oxide, 100+ players | 16 GB | 24-32 GB | Plugins like Backpacks, Friends, Economics increase usage |
| Modded with custom maps, 200+ | 24 GB | 32-48 GB | Custom monuments and assets increase baseline |
Rust servers have a well-documented memory leak issue that worsens over time. Plan for extra RAM headroom and schedule daily server restarts at off-peak hours to mitigate this.
Storage: NVMe Gen 4 for Map Saves and Backups
Rust saves the entire world state to disk every 30-60 minutes (configurable via server.saveinterval). A mature Rust server with an active player base can have a save file exceeding 2-5 GB. The save operation must complete quickly to avoid tick stutters.
- Minimum: 256 GB NVMe Gen 3 (50-100 players)
- Recommended: 1 TB NVMe Gen 4 (100-300 players)
- Large servers: 2 TB NVMe Gen 4 with separate backup NVMe
Do not use SATA SSDs for Rust server hosting. The sequential write speed of SATA SSDs (500-550 MB/s) will cause noticeable lag during world saves once your server save exceeds 1 GB.
Network Requirements
Rust is relatively bandwidth-efficient compared to other games, but player join spikes (map downloads) can saturate your connection:
- Base traffic: 5-15 Kbps per connected player during normal gameplay
- Player join: 5-50 Mbps burst per player downloading the map (map size varies, typically 20-200 MB compressed)
- Port speed: 1 Gbps minimum, 10 Gbps recommended for 200+ player servers with frequent join/leave activity
- DDoS protection: Essential. Rust servers are frequent targets. Look for always-on mitigation at 1 Tbps+
Check the latest dedicated server plans with high-clock CPUs and NVMe storage on our comparison page to find hardware that matches your Rust player target.
Step-by-Step Rust Dedicated Server Setup
Step 1: Install SteamCMD
sudo apt update && sudo apt install -y steamcmd
mkdir -p ~/rust-server
steamcmd +force_install_dir ~/rust-server +login anonymous +app_update 258550 validate +quit
The Steam app ID for the Rust dedicated server is 258550.
Step 2: Configure Server Startup
Create a startup script with optimal 2026 settings:
#!/bin/bash
./RustDedicated -batchmode \
+server.port 28015 \
+server.level "Procedural Map" \
+server.seed 12345 \
+server.worldsize 4000 \
+server.maxplayers 200 \
+server.hostname "My Rust Server" \
+server.description "Vanilla | Active Admins | 2026" \
+server.url "" \
+server.headerimage "" \
+server.identity "server1" \
+rcon.port 28016 \
+rcon.password "changeme" \
+rcon.web 1
Step 3: Configure systemd Service
For automatic restart after crashes:
[Unit]
Description=Rust Dedicated Server
After=network.target
[Service]
User=rust
WorkingDirectory=/home/rust/rust-server
ExecStart=/home/rust/rust-server/start_rust.sh
Restart=on-failure
RestartSec=30
[Install]
WantedBy=multi-user.target
Step 4: Configure Firewall
Open required ports:
- UDP 28015 — Game connection port (default)
- UDP 28016 — RCON port
- TCP 28082 — Web socket (if using web-based admin tools)
Performance Optimization Tips for Rust
- Set worldsize to 3500-4000: The default 4500 is too large for most servers. A smaller map means fewer entities to track and better tick rates.
- Limit entities per player: Use
+server.entityrate 50to cap entity spawns. This prevents players from crashing the server with massive trap bases. - Use Linux over Windows: A Rust server on Ubuntu 24.04 LTS uses 20-30% less RAM than the same server on Windows Server 2022.
- Schedule daily restarts at 4:00 AM: Rust servers accumulate memory fragmentation and entity tracking overhead. A daily restart clears this.
- Disable bradley and patrol helicopters if running near capacity — these NPC entities consume significant CPU for pathfinding.
- Use server-side garbage collection: Enable
+server.gc 1to automatically clean up orphaned entities.
Recommended Rust Server Builds for 2026
| Build | Players | CPU | RAM | Storage | Network | Est. Cost/Month |
|---|---|---|---|---|---|---|
| Starter | 50-100 | Ryzen 5 7600X (6c/12t) | 16 GB DDR5 | 500 GB NVMe | 1 Gbps | $60-100 |
| Standard | 100-200 | Ryzen 7 7800X3D (8c/16t) | 32 GB DDR5 ECC | 1 TB NVMe Gen4 | 1 Gbps + DDoS | $100-180 |
| High Performance | 200-350 | Ryzen 9 7950X (16c/32t) | 48 GB DDR5 ECC | 2 TB NVMe Gen4 | 10 Gbps + DDoS | $200-350 |
| Ultra | 350-500 | Threadripper 7980X / EPYC | 64 GB DDR5 ECC | 4 TB NVMe RAID | 10 Gbps bonded | $400-800 |
Check the full hardware specs on our dedicated server comparison page to find a provider offering the CPU clock speeds and RAM configuration your Rust server needs. With the right bare-metal hardware matched to your target population, your Rust community will enjoy smooth, lag-free gameplay through every wipe cycle.


Leave a Reply
You must be logged in to post a comment.