Rust Server Hosting Requirements, Sized Honestly
Rust server hosting requirements by world size and population: how much RAM and CPU a wipe cycle really needs, and what makes a server stutter.
Rust server hosting requirements are easy to get wrong in both directions. Buy too little and the server stutters through every raid. Buy too much and you pay every month for memory nothing ever touches. Two numbers decide most of it: how big your map is, and how many plugins you run. Your player count is not one of them.
The short answer to Rust server hosting requirements#
Start from the map you intend to generate and the population you really expect on a Friday night, not the peak you hope for. Map size is set by one setting, server.worldsize, and it is the biggest driver of what the server holds in memory.
| What you are running | Plan tier | Why |
|---|---|---|
| Small vanilla map, friends and a few regulars | Survivor (40P+) | A modest world with a settled population is a small job, and the entry tier holds it. |
| A 3500 world with around 50 players and a handful of plugins | Raider (75P+) | The sizing we quote in our quickstart: that map and that population want several GB, plus room for plugins. |
| A large map, a public community, an active plugin set | Warlord (125P+) | More terrain, more built structures, and more plugin state, all resident at once. |
Those are starting points with headroom, not ceilings to run at. A server living at the top of its memory allocation is one heavy wipe night away from swapping, and swapping feels like the whole map lurching.
World size is the memory bill#
Rust builds the world once at wipe and then holds it, whether ten people are online or a hundred. A larger server.worldsize means more terrain, more monuments, and more room for players to build things the server tracks for the rest of the wipe. The jump is not gentle either: the map is a square, so doubling the size number roughly quadruples the area.
The other consumers, in rough order:
- Entities. Every foundation, wall, box, and sleeping bag is an entity the server owns for the rest of the wipe. A month into a busy wipe, player-built structures are usually the largest thing in memory, which is why servers feel heaviest right before the wipe and lightest right after.
- Plugins. Oxide and Carbon plugins are C# files that load live, and the useful ones keep state: kits, economy balances, teleport histories, raid logs. Our Rust quickstart puts it bluntly, because it is true: plugins are the biggest single source of lag and crashes on a Rust server. Add a few at a time and read the console.
- Player count. Real, but smaller than people expect. Each player costs network and simulation work rather than a big block of memory. A hundred players on a small map is a lighter server than fifty on a huge one.
- Backups and saves. The save file grows through the wipe, and a scheduled backup needs free disk to write into, so the storage figure on a plan is not spare capacity. See game server backups and schedules.
Why more memory is often not the fix#
This is the part that saves people money. Rust runs its world simulation largely on one thread, so the speed of a single core decides whether a raid feels responsive or soupy. Memory does nothing for that. Clock speed does, which is why our game nodes run AMD EPYC 4000 or Intel Xeon 6300 series processors at 4.3 GHz and up, on NVMe storage doing better than 1 GB/s, rather than a pile of slow cores. We also cap every node at 60% average CPU load, so the headroom is there when a server is full and raiding rather than sold to somebody else.
Two symptoms, two different purchases. If the server hitches for a second and recovers, over and over, look at plugins first. If it degrades steadily as population climbs and never crashes, that is CPU. If it fills memory and then dies, that is the one case where buying more memory is the answer.
Wipe day is the number to plan for#
Facepunch forces a map wipe on the first Thursday of each month alongside the client update, and plenty of servers wipe weekly on top of that. Wipe day is your peak: everyone logs in at once, the map generates fresh, and every returning player loads terrain in a different direction. A plan sized for a quiet Tuesday is the plan that stutters on the night your community is judging you.
Two practical notes for that window. Old server builds refuse new clients after a Rust update, so restart from the panel to pull the current build and update Oxide or Carbon in the same window. And take a backup before you delete anything, since the game port, the RCON port, and the Rust+ companion port each need their own allocation to come back up the way you left them.
What our Rust plans give you#
Our Rust server hosting plans are sold by resources rather than by player slots, so a regular bringing a friend never costs you anything. These are live figures, read from the same data the order pages use:
| Plan | Memory | vCPU | Storage | Monthly |
|---|---|---|---|---|
| Survivor (40P+) | 8 GB | 2 | 20 GB NVMe | $12.99 |
| Raider (75P+) | 10 GB | 3 | 40 GB NVMe | $19.99 |
| Warlord (125P+) | 12 GB | 4 | 60 GB NVMe | $25.99 |
The player figures in those plan names are guidance for how far each tier stretches, not a cap enforced in billing. vCPU is the slice of a physical core the plan reserves for you, and it stays reserved when a neighbour gets busy.
When to move up, and when to move off a panel entirely#
Watch the panel graphs for a full wipe cycle before deciding. Memory that climbs from wipe day and sits near the ceiling by week three is a sizing problem, and moving between our tiers is a prorated upgrade you can do mid-cycle. Lag that tracks player count instead is a plugin audit and a clock-speed question.
There is a third case. Once you are running a Rust server plus a Discord bot, a stats site, and a database, a machine with root access starts making more sense than a panel. We worked through that trade in game server hosting versus a VPS, and the arithmetic behind Minecraft server RAM requirements applies once you size the box yourself.
FAQ#
How much RAM does a Rust server need?
For a 3500 world with around fifty players, several GB plus room for your plugin set, which is what our middle tier is built around. A small map for friends runs comfortably on the entry tier. A large map with a public population and an active plugin list belongs on the top tier.
Does world size or player count matter more?
World size, by a clear margin. The map and everything built on it stay resident whether ten people are online or a hundred. Player count adds simulation and network work, but it is not what fills memory.
Why does my Rust server lag at the end of a wipe?
Because a month of building has left the server tracking every structure on the map. That is normal, and it is part of why the wipe cycle exists. If it hurts well before wipe day, reduce world size next wipe or move up a tier.
Do Oxide and Carbon plugins change the requirements?
Yes, more than most people budget for. Plugins hold their own state in memory and run on the same thread as the game loop, so a heavy set costs both memory and tick time. Add them a few at a time so you can tell which one hurt.
Can I run a Rust server on a VPS instead?
You can, and it makes sense once you want several services on one machine. You take on the operating system, the updates, and the modding framework yourself, in exchange for root access.