How to set up a Rust server: the wipe cycle and resource planning

A Rust server's resource profile differs from other survival games at one point: world size and the wipe cycle. Hardware chosen without planning those two falls short on the first busy evening.

World size decides everything

The +server.worldsize parameter directly determines both RAM and start-up time:

Map generation is a single-threaded operation; on the first boot the server does not accept connections. Interrupting the process produces a corrupted save. You can see which plan the RAM figures in the table correspond to on the virtual server plans; picking a plan before deciding on worldsize usually means being one step off.

The wipe cycle

In Rust the world is reset periodically. The longer the gap between wipes, the more structures are saved, and with them both RAM and save time grow. The practical consequence: a server that wipes weekly and one that wipes monthly need different hardware at the same player count.

If you are planning monthly wipes, pick RAM one step higher.

Installation

Install with the Ubuntu 22.04 template and download the Rust dedicated server with SteamCMD (app 258550). Then decide on the launch parameters:

./RustDedicated -batchmode +server.port 28015 \
  +server.identity "server1" +server.worldsize 3500 \
  +server.seed 12345 +server.maxplayers 100 \
  +rcon.port 28016 +rcon.password "STRONG_PASSWORD"

The remaining steps, in order:

1. Open the ports: 28015 UDP (game), 28016 TCP (RCON), 28082 TCP (optional web panel).
2. Be very careful about exposing the RCON port — RCON is full control of your server. Where possible, allow only your own IP address.
3. If you are going to install Oxide/uMod plugins, start the server once cleanly and wait for the configuration files to be created.

Record your +server.seed

The seed and worldsize together determine the map. If you do not write both down somewhere, you cannot generate the same map again — and when a reinstall is needed players land in a completely different world.

CPU

Rust runs the world simulation largely on a single thread. On a 100-player server 6-8 vCPU is the practical upper bound; more than that gives no measurable gain. If FPS drops at peak hours, the answer is not adding cores but upgrading the processor family or reducing the plugin/entity load. The general logic of the calculation: how many vCPUs and how much RAM?

That is why raising +server.maxplayers stops adding capacity past a point and only makes more players share the same latency. The full calculation, built on roughly 80 MB per player against a fixed world load of 6-10 GB: game server slot planning

Storage

The Rust installation alone is 15-25 GB, and saves and backups accumulate according to the wipe cycle. 100 GB is the practical baseline; if you are planning monthly wipes and regular backups, 160 GB is more comfortable. Storage can be picked alongside the other resources, with the monthly total shown in the server configurator.

Latency matters as much as capacity, because Rust writes the world to disk at regular intervals (server.saveinterval, 600 seconds by default). As the end of a wipe approaches the number of saved structures grows, that write takes longer, and players feel a brief stutter at save time. Why storage latency shortens that pause by multiples: what is an NVMe SSD?

Official sources

The official documentation behind the ports, app IDs and configuration details in this guide:

• Facepunch Rust Wiki: Creating a server — SteamCMD app ID 258550, server.worldsize, ports 28015 (UDP) and 28016 (RCON)

Next step

We have put the recommended plans by player count and the Rust-specific questions on one page: Rust server plans.