Rust Dedicated Server: Hardware and Network Setup for 100+ Players

Rust is one of the few games where the server’s hardware genuinely shapes how the game feels at 3 AM on wipe day. The server simulates a fully persistent world — every structure, loot container, deployable, and monument must be tracked and synchronized to players who may be anywhere on a 4,000-meter map. That workload is why a dedicated server for game hosting beats a VPS for Rust: no noisy neighbors stealing CPU time from a simulation that runs a continuous tick loop. Here’s what a Rust box actually needs, from a 50-player community server to a 500-player mainline.

What Rust’s server does with your hardware

Rust’s server architecture is a single continuous simulation that processes players, entities, and world state every frame. Unlike Minecraft’s 20 TPS loop, Rust runs its simulation at a higher internal rate, and the cost scales with three things: player count, entity count (buildings, loot, barrels, animals, monuments), and map size. A 4,000-map with 300 players and 200,000+ entities is a different workload than a 3,000-map with 60 players. The practical effect: Rust is CPU-heavy first, RAM-heavy second, and storage-dependent in ways most admins discover only after their save files balloon.

Target players	CPU	RAM	Storage	Bandwidth
50–75	4 cores @ 3.5 GHz+	12–16 GB	NVMe (save + world)	100 Mbps
100–150	6 cores @ 3.7 GHz+	16–24 GB	NVMe, 500 GB+	250 Mbps
200–300	8–12 cores @ 3.7 GHz+, high IPC	24–32 GB	NVMe, 1 TB+	500 Mbps–1 Gbps
400–500	12+ cores, best single-thread available	32–48 GB	NVMe RAID, 2 TB+	1 Gbps

CPU: cores for the simulation, speed for the tick

Rust scales across more cores than Minecraft does, but the main simulation still has serial sections, so single-thread performance remains critical. For 100+ players, look for a modern server CPU with a base clock of 3.5 GHz or higher and strong turbo behavior — EPYC 4004-series or Xeon E-2400/E-2500 class parts are typical. If you plan to run Oxide plugins (the plugin framework used by most community servers), budget one extra core or two: plugin hooks run on the server thread and consume real CPU at high player counts.

RAM: the 16 GB floor

Rust’s server process routinely uses 8–12 GB with a 200+ player population, before the OS file cache and any monitoring tools. The practical minimum for a serious community server is 16 GB of RAM on the box; 32 GB gives headroom for the save, entity tracking, and the OS cache that keeps world streaming fast. One detail that surprises new admins: Rust saves are large and frequent. A busy server with 300 players can produce save files in the 2–10 GB range, and the save process writes to disk while the world keeps simulating — which is where storage speed starts to matter.

Storage and network: where Rust differs from other games

Put the Rust install and the save directory on NVMe. During save cycles, the server snapshots world state to disk; on a SATA SSD this shows up as micro-stutter at peak times, and on HDDs it can cause visible freeze frames. The Rust client downloads the map and any custom content from your server, so a fast disk also helps players connect faster on wipe day — a 4,000-map with heavy monuments can be several hundred MB.

On the network side, Rust uses UDP port 28015 for game traffic (TCP 28016 for RCON, 28017 for the app port in newer builds). Per-player usage runs roughly 0.3–1.0 Mbps at the server, so 100 players needs 30–100 Mbps of clean, uncongested upload — and public community servers typically pick a 1 Gbps port so the 100–200 Mbps spikes during raid hours never hit the cap. If you are estimating total requirements across several games, the numbers in our game server bandwidth breakdown give per-game baselines.

A minimal working setup

For a 100-player community server, this is a sane starting point:

# steamcmd (run as a dedicated user)
steamcmd +force_install_dir /opt/rust +login anonymous \
  +app_update 258550 validate +quit

# startup script (RustDedicated)
/opt/rust/RustDedicated -batchmode +server.port 28015 \
  +server.level "Procedural Map" +server.seed 12345 \
  +server.maxplayers 100 +server.worldsize 4000 \
  +server.saveinterval 300 +server.tickrate 30 \
  +rcon.port 28016 +rcon.password "CHANGE_ME"

After the first launch, bump server.tickrate only if the box has headroom — 30 is a good default for 100 players; 64 tick on a busy server needs a seriously fast CPU. Then set up Oxide (oxide mod via uMod) only after the vanilla server runs clean, and test wipe-day load with a full map download before opening the doors.

Right-sizing the box

The difference between a Rust server that holds 100 players at a steady tick and one that stutters through raid hour is usually the CPU’s single-thread speed and a fast NVMe save target, not RAM quantity alone. Start from the player tiers above, and remember that plugin-heavy or modded setups need one step more CPU and RAM than vanilla at the same population. To compare machines with the right specs for your target population, check the dedicated server plans on our comparison page — or, for a quick price anchor, look at InterServer’s dedicated server options, which offer Intel and AMD configs that map directly to the tiers above.