Skip to main content
GameServerPlan
Get started

Rust

Rust Server Planner

Four questions, then we read Facepunch's published figures for your situation. Every figure you see is theirs. Which of them matters most to you, and how we describe your server, is ours.

Facepunch ties this to the processor, never to memory. Any whole number.

players at once

The wiki's range is 1000 to 6000, and size drives memory and disk.

Our own read — the official page does not cover modded servers.

Also ours. Longer gaps let more get built before the reset.

Answer all four to see a recommendation.

How this works, and what it will not do

Facepunch's wiki publishes one set of figures and names two things that pull on them: map size moves memory and disk, and player population moves the processor. It gives the direction of both without ever quantifying them. So this planner calculates nothing — it weighs your answers and tells you which published figures matter and which way they lean.

  • It will never turn a player count into an amount of RAM. Facepunch ties population to the processor, and we keep that relationship where they put it.
  • It will not convert a map size into gigabytes, or name a core count, clock speed or CPU model. None of those appear in the source.
  • Plugins and wipe length are our reading, labelled as ours throughout. No RAM is assigned per plugin or per week between wipes.
  • Where the evidence does not support a higher figure, it says headroom may be sensible. Rust's wiki publishes one memory figure, so an invented 16, 24 or 32 GB tier would be exactly that — invented.

The full published list, and what the wiki says can change it, is on the Rust server requirements page. Whether your own machine is the right place to meet those figures is a separate question, and self-host or rent is where we weigh it up.

Back to Rust