Rust Dedicated Server Specs: RAM, CPU, and Tick Rate for 100+ Players

Rust is one of the heaviest games you can run on your own hardware. A single 100-player server on a 4,000-meter map, loaded with a few dozen Oxide plugins, will routinely hold 12–16 GB of RAM and keep four or more CPU cores pinned near 100% in the hours after a wipe. If you are planning a Rust server for 2026 — or moving one off a host that keeps crashing on wipe night — the hardware decisions below matter more than any config tweak. This guide covers the RAM, CPU, storage, and bandwidth specs that determine how many players your box can actually carry, plus the tick-rate and garbage-collection settings that squeeze the most out of it.

What Actually Drives Load on a Rust Server

Rust does not behave like a traditional FPS server. The simulation layer tracks every entity on the map — buildings, loot, corpses, vehicles, and monument events — and re-evaluates them at a 30 Hz tick rate. That entity simulation, not the raw player count alone, is what consumes CPU and RAM. A 50-slot server on a densely built 4,500-meter map can out-load a 150-slot server on a fresh 3,000-meter map, which is why copy-pasting someone else’s specs rarely works.

• Entity count — buildings, items, and corpses are the single biggest driver of RAM and CPU usage. Wipe day is the calm; week three is the load test.
• Map size — moving from 3,000 to 4,500 meters roughly doubles the area players can build in, and the entity budget scales with it.
• Plugins and mods — every Oxide/uMod plugin adds per-tick CPU work. Ten economy and raid plugins can cost more than ten extra players.
• Automatic events — heli, cargo ship, and Bradley spawns cause sharp CPU spikes that expose under-provisioned boxes.

RAM: Where the “8 GB Is Enough” Advice Falls Apart

Facepunch’s official minimum is 8 GB, and that is true for a 20–30 slot vanilla server. It stops being true the moment you cross 50 slots, add plugins, or run a map larger than 3,000 meters. Owners who under-buy RAM end up with OOM-killed processes and corrupted world saves — the two most common causes of “my Rust server disappeared” threads. Budget for headroom, and prefer ECC memory on anything that will run for weeks between wipes, because a flipped bit in a world save is not something a reboot fixes.

Player slots	RAM (vanilla)	RAM (modded)	Notes
50	6–8 GB	10–12 GB	Fine on 3,000-meter maps
100	10–12 GB	14–16 GB	The most common community size
150+	14–16 GB	20+ GB	Plan for 4,000+ meter maps

CPU: Core Count vs Clock Speed for Rust

Rust’s simulation is largely single-threaded, which is why a fast 8-core processor beats a slow 16-core one for a single server instance. That said, the server process, Oxide, the operating system, backups, and monitoring all want cores too. The practical sweet spot is 8 physical cores at 3.5 GHz or higher — a modern AMD EPYC 7003/9004 series or Intel Xeon Silver/Gold class chip. If you plan to run two Rust instances on one box (common for a main server plus a staging or PvE server), step up to 12–16 cores and 32 GB or more of RAM.

Server size	CPU recommendation	Typical chips
50 slots	6 cores @ 3.5+ GHz	Ryzen 7 class / EPYC 7313
100 slots	8 cores @ 3.5–3.8 GHz	EPYC 7443P / Xeon Gold 6330
200+ or dual instance	12–16 cores, split across instances	EPYC 7543P / Xeon Gold 6348

Storage and Bandwidth: NVMe, Wipe Day, and Update Day

Rust writes its world save constantly, and wipe day plus forced update day produce heavy burst I/O. A SATA SSD handles small servers, but 100-slot boxes on NVMe see measurably fewer save hitches and much faster restarts after a crash. On the network side, plan for roughly 2–3 Mbps per player during peak play, and far more on update day when everyone downloads simultaneously. A 100-player server should sit on at least 250 Mbps of high-capacity bandwidth, with room for the monthly forced-wipe download spike.

Player slots	Typical peak bandwidth	Storage minimum
50	100–150 Mbps	500 GB NVMe
100	250–400 Mbps	1 TB NVMe
150+	500 Mbps–1 Gbps	2× 1 TB NVMe (mirror)

Setup Checklist: Tick Rate, GC, and Backups

• Keep tickrate at the default 30 — forcing 60 on a shared box causes more lag than it cures.
• Tune gc.interval and gc.mbps so garbage collection smooths out instead of hitching every few minutes.
• Automate world backups on a schedule and keep at least the last three on separate storage from the live save.
• Pin the server process to physical cores with taskset when the box runs other workloads alongside Rust.
• Watch for OOM kills and CPU steal with htop or netdata — both are early warnings that the box is undersized for your wipe cycle.

Choosing Hardware for Your Rust Server

None of these specs require exotic hardware. A single-tenant dedicated box with 8 fast cores, 16 GB of ECC RAM, and NVMe storage is a proven 100-slot Rust configuration, and it costs less per month than renting the equivalent as a managed game-server slice once you add up per-slot markups. To see how current providers price these builds — and which data centers give your player base the best ping — compare dedicated server plans on our comparison table.

InterServer’s dedicated lineup is a reasonable starting point: single-tenant Xeon and EPYC machines with NVMe options, priced flat without the per-slot fees game hosts add. Check InterServer’s current dedicated server pricing if you want a direct quote for a 100-slot Rust build. Whichever provider you choose, spec for week-three entity counts, not launch-day ones — that is the difference between a server that lasts a wipe cycle and one that dies mid-month.