LearnDocsLog in
Deploy a serverDeploy

Rust server requirements

What a Rust server needs in CPU, memory, disk and bandwidth, by player count. Change the numbers for your own server; the sources are listed below.

Plugins (Oxide/uMod)
Assumptions

What it needs

CPU
3 coresSingle-thread heavy: clock speed matters more than core count.
Memory
11 GB
NVMe storage
25 GB
Traffic per month
170 GB
Busiest upload
1.5 Mbit/s

On Clouduxe

Fits your load

VPS Pro

6 vCPU, 12 GB DDR5, 120 GB NVMe, 8 TB traffic

₹5,340$56.49/mo

Deploy ProAbout Pro

Room to grow

VDS FusionCore

4 dedicated cores, 16 GB DDR5, 200 GB NVMe, 10 TB traffic

₹9,940$104.49/mo

  • 4 dedicated cores instead of 6 shared vCPU: the game's main thread gets cores no other customer uses.
  • 4 GB more memory, 80 GB more NVMe.
  • Headroom for busy evenings, more players, and the mods and updates you add later.
Deploy FusionCoreAbout FusionCore

By player count. Without plugins (oxide/umod); each step up in the calculator adds memory, disk and sometimes a core.

PlayersCPUMemoryNVMeTraffic a monthFits your loadRoom to grow
102 cores7 GB25 GB34 GBVPS GrowthVDS MicroCore
503 cores11 GB25 GB170 GBVPS ProVDS FusionCore
1004 cores16 GB25 GB340 GBVPS EliteVDS FusionCore
1505 cores21 GB25 GB510 GBVDS OmniCoreVDS PrimeCore
2006 cores26 GB25 GB680 GBVDS PrimeCoreVDS TitanCore
3009 cores35.5 GB25 GB1 TBVDS TitanCoreVDS UltraCore
50014 cores55 GB25 GB1.7 TBVDS UltraCoreBare metal

Traffic assumes 35% of the player cap online on average across the month; change it under Assumptions in the calculator.

Where the numbers come from. Published figures first, then how the calculator turns them into a model.

Published requirements

  • 12 GB free RAM (6k map will use more); 15 GB free disc space (SSD/NVMe highly preferred). The more players, the faster your computer CPU needs to be. These values are not fixed and highly depend on the use case and population of the server.

    Creating a server - Rust Wiki (official)

  • Minimum RAM requirements is 4GB of RAM, but 8GB+ is recommended for optimal performance. Processor: Dual-core 3.4GHz or greater. Disk Space: 32GB+. Network: Minimum 100Mbps+, Recommended 1Gbps.

    What are the RUST Dedicated Server Requirements? - ServerMania KB

  • The Rust game server process will take up from 6 to 10GB RAM, depending on your map size (12-16GB and more is recommended). It will also use constantly 50-65% of one core from a Xeon E5-1650V3 (6 cores 12 threads, 3.8Ghz). Prefer good monothread performance: a quad/hexa core @3.3Ghz+.

    Rust - LinuxGSM Wiki

How the model is built

Memory
6 GB plus 100 MB per player. Base 6GB matches Facepunch's own note that the server process uses 6-10GB just for a loaded map before any players (LinuxGSM wiki) and the official wiki's 12GB free-RAM minimum. +100MB/player scales it to roughly 11GB at 50 players, 16GB at 100 (matches community 50-100 player guidance of ~16GB), and 26GB at 200 (matches the 24GB+ figure widely quoted for 100+ player servers). Map/world size, not player count, is the single biggest driver of Rust RAM use.
CPU
2 cores, one more for every 40 players. Rust's main tick is bound to a small number of threads, so clock speed matters more than core count (LinuxGSM wiki: server used 50-65% of a single 3.8GHz Xeon core; recommends a quad/hexa core at 3.3GHz+ for a live server). ServerMania's dual-core 3.4GHz minimum sets the 2-core floor. playersPerExtraCore=40 pushes to 3-4 cores by 100-160 players and 6 cores by 200+, matching the quad/hexa guidance.
Disk
15 GB for the server plus 10 GB for saves and backups, on SSD or NVMe. installGB is Facepunch's own official figure (15GB free disc space). growthGB covers larger world sizes (map data grows with worldsize up to 6000), plus saves, backups and wipes over time. SSD/NVMe is explicitly recommended by Facepunch and by hosting guides.
Bandwidth
30 kbit/s of upload per player. Derived from Rust community bandwidth discussion (Oxide forum): a 100-slot server needs roughly 1-5 Mbps constantly, and ~20kbps per player for movement alone is 'fine' in steady state; 30kbps/player upload is a middle-of-range planning figure that leaves headroom for raid/monument spikes.
Plugins (Oxide/uMod)
Memory times 1.25 for some and 1.6 for heavy; a heavy load also adds a core.

Facepunch's own minimums (12GB RAM, 15GB disk) are not tied to a specific player count; they scale mainly with map/world size and entity count. Player-count scaling of RAM and CPU above is derived from community and hosting-provider guidance layered on top of the official baseline, not a single official table. Modded (Oxide/uMod) servers vary widely in resource use depending on which plugins run.

Before you set it up. The ports it listens on and what the guides say drives its load.

Ports

PortProtocolUsed for
28015UDPgame
28016TCPrcon/app (Rust+)

Game server hosting: every game we size, the protection each one gets, and the plan for it.

DDoS protection is on every Clouduxe plan. How Prism protects Rust servers.

What drives the load

  • World size drives RAM more than player count: a 6000 map loads several GB before a single player connects.
  • Rust is single-thread bound per tick, so a higher clock speed helps server FPS more than adding cores.
  • Oxide/uMod plugins add ongoing RAM and CPU overhead; heavily modded servers can need noticeably more than vanilla at the same player count.
  • SSD/NVMe storage is explicitly recommended by Facepunch and hosting guides because map saves and autosaves are disk-intensive.

Rust server questions

Talk to us
How much RAM does a Rust server need?

About 7 GB for 10 players and 55 GB for 500, before plugins (oxide/umod). Base 6GB matches Facepunch's own note that the server process uses 6-10GB just for a loaded map before any players (LinuxGSM wiki) and the official wiki's 12GB free-RAM minimum. +100MB/player scales it to roughly 11GB at 50 players, 16GB at 100 (matches community 50-100 player guidance of ~16GB), and 26GB at 200 (matches the 24GB+ figure widely quoted for 100+ player servers). Map/world size, not player count, is the single biggest driver of Rust RAM use.

How many CPU cores does a Rust server need?

2 for 10 players, 14 for 500. The server is single-thread heavy, so the clock speed of one core matters more than how many cores it has. Rust's main tick is bound to a small number of threads, so clock speed matters more than core count (LinuxGSM wiki: server used 50-65% of a single 3.8GHz Xeon core; recommends a quad/hexa core at 3.3GHz+ for a live server). ServerMania's dual-core 3.4GHz minimum sets the 2-core floor. playersPerExtraCore=40 pushes to 3-4 cores by 100-160 players and 6 cores by 200+, matching the quad/hexa guidance.

How much bandwidth does a Rust server use?

About 30 kbit/s of upload per connected player, so 1.5 Mbit/s with 50 players online and about 170 GB a month if 35% of that cap is online on average. Derived from Rust community bandwidth discussion (Oxide forum): a 100-slot server needs roughly 1-5 Mbps constantly, and ~20kbps per player for movement alone is 'fine' in steady state; 30kbps/player upload is a middle-of-range planning figure that leaves headroom for raid/monument spikes.

Which Clouduxe plan should I pick for Rust?

For 50 players, VPS Pro fits the load and VDS FusionCore leaves room to grow. Every plan includes DDoS protection: 17 Tbps of upstream mitigation plus Clouduxe Prism on the server.

Other games. The same calculator, sized from each game's own documentation.

All calculators

Host Rust on VPS Pro.

Sized for 50 players, with DDoS protection included. Or talk to us about a bigger server.

See VPS ProSize another server