Finding and Setting a Rust Server Map Seed

A Rust map seed, together with the world size, determines which procedural map your server loads. For a community server that plays well, you should not choose the seed randomly, but check monuments, spawn areas, roads, coastlines, and the expected player count before the wipe. This helps you avoid unfair hotspots and walking distances that are too long.

What a Rust Map Seed Does

A seed is the numerical basis from which Rust generates a procedural map. What matters is this: the seed alone does not determine the map; the combination of seed, map size, and map type does. The same seed plus the same map size results in the same procedural map. The same seed with a different size, however, generates a different map.

Facepunch explains on the official Rust wiki page for Map Data that procedural maps are generated from size, seed, and map type. For Procedural Map, the value ranges listed there are size 1000-6000 and seed 0-2147483647. These values are a useful technical guardrail, but they do not replace checking how the map actually plays.

For game-serverhosting, the seed is mainly an operating parameter: it lets you plan, communicate, and test in a controlled and repeatable way. This is especially useful when you are preparing wipes, tuning plugins, or explaining to your community in advance what kind of map will be played in the next cycle.

Setting Seed and World Size

For a procedural Rust map, you need at least a seed and world size. In a server.cfg, the values are written without a leading plus sign:

server.seed 12345
server.worldsize 3500

If you use startup parameters instead of server.cfg, the values are typically set with plus signs, for example +server.seed 12345 +server.worldsize 3500. Facepunch shows this format in the official guide to creating a Rust server. In practice, the important thing is that only one unambiguous configuration is active in the end. Avoid conflicting values in the panel, startup line, and configuration file.

After a change, you must restart the server so the world is loaded with the new values. It is best to plan this directly with the next wipe, because changing the seed affects the world structure and existing bases, loot locations, and routes cannot reasonably be preserved.

Using Seed Finders Effectively

A practical tool is rustmaps.com – there you can generate and filter maps. Use tools like this not just for quickly clicking through maps, but with a clear checklist: Which monuments must be present? How far are Outpost and Bandit Camp from typical spawn zones? Are there enough recyclers? Is Launch Site reachable without dominating the map?

If you want to approach Rust administration in a more structured way overall, the internal guide Rust Server Commands – All Admin Commands 2026 fits well with this. For preparation around wipes, the Rust Wipe Calendar 2026 is also helpful, because seed selection and wipe communication belong together.

Criteria for a Good Map

The table is a starting point, not a strict rule. For PvP-heavy servers, the map can be more compact and conflict-heavy. For more relaxed community servers, more even routes and several usable building areas are more important. Also check whether large monuments push out all attractive building areas and whether new players have realistic options after spawning without immediately running into the same bottleneck.

Choosing the Right Map Size

A larger map does not automatically mean a better player experience. It can make routes longer, reduce encounters, and require more resources to operate. A map that is too small, on the other hand, can increase spawn pressure, doorcamping, and monument congestion. So choose the size based on real activity, not just maximum slots. If you are still working on the basic setup, the guide Renting and Setting Up a Rust Server – The Complete Guide helps with the remaining server parameters.

Checking the Result

After the restart, you should check whether the desired map was actually loaded. Compare the seed and world size in the panel or configuration with the seed finder. Connect to the server, open the map, and check noticeable points such as the coastline shape, Launch Site, Outpost, and Bandit Camp. If these do not match, usually a different value is active or the map was not regenerated.

Record the final seed internally and only announce it publicly if your community expects that. For planned server cycles, a short note is useful: wipe date, seed, world size, map concept, and any special notes on monuments or rules.

Custom Maps Instead of a Seed

As an alternative to seeds, you can use custom maps:

1. Create the map in RustEdit
2. Export it as a .map file
3. Upload it to the server
4. In the startup line: +server.levelurl "<YOUR_HTTPS_MAP_URL>"

Facepunch explains on the official Rust wiki page for Hosting Custom Maps that with +server.levelurl [url], the map is loaded from that URL and procedural parameters such as +server.worldsize or +server.seed should be removed. So use either a procedural map with seed and world size or a custom map with a level URL, but not both at the same time.

Troubleshooting

If the seed is not applied, first check for duplicate configurations. One value in the hosting panel, another in the startup line, and a third in server.cfg quickly lead to confusion. Make sure the server was really restarted and that no old world is being reused.

If players see a different map than expected, compare the seed, world size, and map type. Even a different size is enough to create a completely different map. For custom maps, the URL must be directly accessible. If a download page appears in the browser first, it is usually unsuitable for server.levelurl.

If the map plays poorly, that does not necessarily mean there is a technical error. In that case, before the next wipe you should specifically look for a different monument distribution, safer zones that are easier to reach, or a smaller or larger world size.

Verification, Limits, and a Safe Rollback

The guide “Finding and Setting a Rust Server Map Seed” applies to the server type described in the article and the version state visible at the time of verification. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them first.

Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step at a time and test it with the same client and server version you want to play with later.

A successful single test is not a guarantee of performance or availability. World size, mods, plugins, player count, network route, and simultaneous load can change the result. Document the version, change, and test result so you can trace later differences.

FAQ

What is the best Rust map seed?

There is no universally best seed. A good seed fits the player count, server concept, and desired PvP density. Check monuments, safe zones, recyclers, and travel routes before the wipe.

Does the map stay the same if I only know the seed?

Only if the world size and map type are also the same. The same seed with a different map size generates a different map.

Which world size should I choose for a community server?

For many community servers, 3500 is a sensible starting point. With a small active player base, 3000 may work better; with very high activity, 4000 or more is more likely to fit.

Do I have to restart the server after changing the seed?

Yes. Seed and world size take effect when the world is loaded or generated. So plan changes cleanly with a wipe and a restart.

Can I use a seed and a custom map at the same time?

In practice, you should choose one. A procedural map uses seed and world size. A custom map uses server.levelurl; procedural parameters should be removed for that.