Calculating RAM and Map Size for a Rust Server
RAM for a Rust server: the 12 GB floor Facepunch publishes, map size and player count, and how memory climbs across the wipe cycle.
Calculating RAM and Map Size for a Rust Server
The most common mistake when renting a Rust server is sizing the package around day one of the wipe. A server that runs comfortably on the 12 GB baseline Facepunch states, on a freshly generated map, starts stuttering in the last week of the month with exactly the same player count. This article explains what actually drives the RAM requirement, how map size factors in, and which day of the cycle you should be sizing for.
The Three Variables That Determine Memory Usage
Memory usage on a Rust server does not come down to a single number. Three variables work together:
| Variable | Effect | Behaviour over time |
|---|---|---|
| Map size | Baseline memory usage | Constant |
| Player count | Real time processing and network load | Fluctuates hourly |
| Entity count | Persistent memory usage | Climbs continuously through the wipe |
The most deceptive of the three is the entity count. Every wall, chest, door and trap players build is an object the server holds in memory. Even with a flat player count, the number of structures in the world by week three of a wipe is several times what it was on day one.
The Only Figure Facepunch Publishes: 12 GB
The official Rust wiki states a single memory figure for the server, 12 GB of free RAM, and adds that maps above 6,000 will want more than that. Beyond that, no official per map size RAM table is published.
The tiers below sit on top of that 12 GB baseline and come from our own measurements, not from an official source. They were observed on a server with a standard plugin setup, around mid wipe (roughly day 15):
| Map size | Typical players | Our own measurement | Note |
|---|---|---|---|
| 3,000 | 10-40 | 12 GB | The baseline Facepunch states is enough |
| 3,500 | 40-80 | 16 GB | The most common choice |
| 4,000 and above | 80-150 | 20 GB and above | Where dense building starts |
💡 Going from a 3,000 map to a 3,500 map grows the world area by roughly a third. That is not just more space, it is more trees, animals, monuments and buildable ground.
How Memory Grows Across the Wipe Cycle
On a server with a monthly wipe, the typical progression looks like this:
- Days 1-3: Baseline usage. Few structures, memory usage at its lowest.
- Days 4-10: Base building finishes and the entity count climbs quickly.
- Days 11-20: Large clans expand and memory usage reaches 1.5 to 2 times the day one figure.
- Days 21-30: Peak. If the server stutters on these days, the package is undersized.
This is why you should size the package around the last week of the month. A package chosen based on how comfortable day one felt will cost you players by the end of the month.
Is Shrinking the Map Always the Answer?
No. A smaller map lowers memory usage, but it also cuts the space available per player. On a 3,000 map with 150 players there is nowhere left to build a base, players constantly get in each other’s way, and the server empties out. The practical ratio we use is:
Recommended map size ≈ 2,500 + (active player count × 12)
For a server with 80 active players that works out to roughly 3,500, which matches the tier above. This formula is not official either; it is a summary of our own experience.
Two Things Beyond Memory That Get Overlooked
1. Processor Speed
Adding RAM will not fix a falling tick rate. Facepunch states on their own wiki that a higher player count needs a faster CPU, and they say nothing about core count. That is why we recommend the high frequency Ryzen Premium VDS line for Rust servers.
2. Disk Speed
Rust saves the world every five minutes. Toward the end of a wipe that save file reaches hundreds of megabytes. On a mechanical or shared disk the operation visibly freezes the server; on NVMe SSD it goes unnoticed.
When Should You Upgrade the Package?
If two of the following apply at once, your package is undersized:
- The server stutters regularly during the last week of the month
- Memory fills back up shortly after
gc.collect - You find yourself having to shorten the restart interval
- Players only complain about “server lag” during peak hours
🚀 You can upgrade your package mid month. Moving up before wipe day and dropping back at the end of the month is a common pattern.
Conclusion
RAM planning for a Rust server depends as much on where you are in the wipe cycle as it does on map size and player count. The right approach is to pick a package sized for the busiest day of the month and not to compromise on processor speed.
👉 For package matching based on your game, see our Rust server rental page, and for the full range of options take a look at our game server rental page.