Rust is one of the most demanding games to host: generated maps, hundreds of structures per player, heavy saves. A successful Rust server comes down to three things: the right map size, well-chosen plugins and hosting that can absorb peaks and attacks.
1. Map size and player count
The map size (server.worldsize) and seed (server.seed) set the load at startup and throughout the wipe. A bigger map holds more players but needs more RAM and generation time.
| Server | Suggested map | Starting RAM |
|---|---|---|
| Small group of friends | 2500 to 3000 | 8 GB |
| Community of 50 to 100 players | 3500 to 4000 | 12 to 16 GB |
| Popular server | 4000 and above | 16 GB and above |
These are starting points: watch usage after a few days, as the RAM needed grows with the number of structures built.
2. Oxide/uMod or Carbon?
Both are plugin frameworks installed on the Rust server:
- Oxide / uMod: the oldest, with the largest plugin library.
- Carbon: a newer, performance-oriented alternative compatible with a large share of Oxide plugins.
Either way, plugins go into a server folder (oxide/plugins or carbon/plugins), so you need hosting with full file access.
3. Wipes
Rust forces a wipe with each monthly game update. Many servers add weekly or bi-weekly wipes to restart the competition. A panel that lets you delete the right map and player files in a few clicks saves a lot of time at every wipe.
4. Why CPU speed matters
As with Minecraft, Rust's server loop depends heavily on single-core speed. A fast processor reduces rubberbanding and tickrate drops in fights. To know what to look at, read our guide on reading a hosting spec sheet.
5. DDoS attacks: the reality of a public Rust server
Rust servers are a frequent target. Always-on protection included in the plan means you do not have to react during the attack: what DDoS protection does and does not do.
What is included with us
Our Rust plans include the Pterodactyl panel, full file access for Oxide or Carbon, 4 GHz machines with NVMe, DDoS protection and a 7-day free trial.