Rust Map Size Explained: What 3000, 4500 and 6000 Actually Mean

Map size in Rust is a single number, and almost everybody reads it wrong. It is not a difficulty setting and it is not a quality setting. It is the length of one side of the world, in metres, and that has consequences most server owners meet only after they have paid for a machine.

Size is a side, so the world grows as the square. A 6000 map is not twice a 3000 map. It is four times the ground, four times the monuments to render, and roughly four times the room for your population to fail to find each other in.

This guide is the arithmetic, the memory cost, and the honest answer to “what size should my server be” — which depends on how many people actually play, not on how many you hope will.

The arithmetic nobody does

Square the number and you have the area in square metres.

• 3000 — 9 km²
• 3500 — 12.25 km²
• 4000 — 16 km²
• 4500 — 20.25 km²
• 5000 — 25 km²
• 6000 — 36 km²

Going from 3000 to 4500 sounds like a fifty per cent increase. It is a 125 per cent increase in ground. Going from 3000 to 6000 is four times the world for a number that looks like double.

And a good part of any map is water and unbuildable cliff, so the playable land grows less than the raw figure — but the server still has to hold all of it.

Open water and icebergs. On a 6000 map you can put this much sea between two places. Sea Skull.

How many players a size needs

The number that matters is not your slot count. It is how many people are actually online at a normal hour. The commonly used ranges, which match what hosts publish and what servers report:

1. 3000 — 20 to 40 players. A small community that knows each other.
2. 3500 — 40 to 80. Facepunch’s own recommended starting point.
3. 4000 — 80 to 130. The common shape for a server aiming at a full hundred.
4. 4500 — 130 to 180.
5. 5000 and up — 180 and up, or roleplay and PvE, where people want space rather than contact.

Too big is worse than too small. A small map with too many people is a meat grinder, and some servers sell that deliberately. A big map with too few is a walking simulator, and nobody has ever sold that. If you are not sure, go one size down.

What it costs in memory

Map size is the largest single driver of a Rust server’s memory use, because the whole world is held resident. Published figures from hosts sit around:

• 3000 — 6 to 8 GB
• 3500 — 8 to 10 GB
• 4000 — 10 to 14 GB
• 4500 — 14 to 18 GB
• 5000 — 18 to 24 GB

Those are running figures, not boot figures, and a Rust server grows through a wipe as players build. Leave 25 to 30 per cent headroom after boot. A server that starts at 10.5 GB on a 12 GB machine has already lost; it will be fine on Monday and crashing by Friday.

Facepunch’s own free community server tier offers 12 GB of RAM and says plainly that a 6000 map will use more than that. That is a useful sanity check on anyone telling you 8 GB is plenty.

Why a custom map costs more than a procedural one

A procedural map is generated from a seed using Facepunch’s own monument set, at the density they tuned. A custom map is a file somebody built by hand, and hand-built usually means denser.

Hosts that publish a figure put a RustEdit custom map at roughly 30 per cent above the procedural figure for the same size. Whether that holds depends entirely on the map: a spare, terrain-led map can cost less than procedural, and a map with six detailed custom monuments on it can cost a great deal more.

So ask the map’s author what the prefab count is before you buy, and run ent count on your own server after the first day. The number that matters to your players is entities, and a server starts visibly struggling somewhere around 150,000 to 200,000 of them on a normal plan.

What size does to the game, not just the machine

The hardware cost is the easy half. The other half is what distance does to how people play, and it is the half nobody budgets for.

Travel time becomes the tax on everything

Crossing a 3000 map on foot is a few minutes. Crossing a 6000 map is a journey, and every journey is a chance to be killed carrying something. On a big map players stop making trips: they hoard, they build near what they need, and whole regions go unused.

That is why big maps need vehicles to work at all. If your server has horses and boats disabled, subtract a size.

Raids get further away, which changes who raids

A raid on a small map is an afternoon. On a large one it is an expedition with a return leg carrying loot. That suits organised groups and punishes solos, so a large map quietly makes your server more clan-friendly whether or not you meant it to.

Monument density is the number that decides the early game

More ground means more monuments, but it also means more ground between monuments. A player who spawns far from anything on a 6000 map has a worse first hour than the same player on a 3000 map, and the first hour is when you lose people who were only trying your server out.

Look at the map render and find the emptiest quarter. Ask yourself what somebody who spawns there does for the first twenty minutes. If the honest answer is “walks”, the map is too big for what is on it.

The two numbers to watch after launch

Server FPS

Type server.fps in the console. A healthy Rust server sits near 30. Below 20 at peak, players feel it: doors open late, shots land late, and vehicles rubber-band.

Save time

Under 500 ms and nobody notices. Between one and two seconds, attentive players see a micro-freeze every save. Longer than that and your map or your entity count is past what the machine can carry.

Check both a week into a wipe, not on launch night. On launch night the world is empty and everything is fast. The question is what it looks like on day seven with three hundred bases on it.

So what size should you run

• Starting a server with no population yet: 3000 or 3500. An empty small map reads as quiet. An empty big one reads as dead.
• Steady 100 players: 4000.
• Steady 150 or more: 4500.
• Roleplay, PvE, or events with space between them: 5000 or 6000, and budget the machine for it.

And whatever you pick, pick the machine to match it rather than the other way round. The most expensive mistake in Rust hosting is a big map on a small box: it works for a week, and then it fails at exactly the moment your server is finally busy.

A landmark you can navigate by. Sea Skull.

Size is not the same as having something to walk to

All of the above is about how much ground there is. None of it is about whether the ground is worth crossing. A 6000 map with nothing on it is not a big world, it is a long walk.

That part is the map itself, which is what I build: custom maps from 3000 to 6000, with monuments made for them rather than scattered on afterwards.