Rust Server Hosting: RAM, Wipes and Oxide Plugin Setup

Rust is the most resource-hungry survival game to host. Map size, player count and entity density all push the same three resources: memory, single-core speed and outbound bandwidth.

Rust punishes under-provisioned servers harder than almost any other game. A map is a live simulation of hundreds of bases, furnaces, electric circuits and animals, all ticking whether players are watching or not. This guide covers Rust server hosting: how to size the box, choose a map, plan wipes, and install Oxide without breaking performance.

RAM and CPU sizing for Rust

Memory scales with map size and player count together, because more players means more bases and more entities loaded at once. Use this as a starting point:

CPU is the other half. Rust simulates AI, physics and decaying entities on a main loop, so high clock speed beats core count. The server also runs background tasks (decay sweeps, save operations) on other cores, so 4 fast cores is the sweet spot: a Ryzen 7 or a modern Xeon with strong single-core performance. Storage must be NVMe. World saves on Rust are large and frequent, and a mechanical or slow SATA drive produces visible hitching during the save cycle.

Choosing a map size, seed and spawn population

Map size should match your community, not your ambition. A 4500 map with 40 players feels empty and dead, and players leave servers that feel empty. For an Indian community of 80-120 players, a 3500-4000 map with a good monument spread gives dense encounters without crowding. Pick a seed with a decent desert or snow biome mix for ore variety, and always generate the map with a wiped folder before you open it - regenerating later deletes everyone's base.

Wipe schedule and communication

The standard cadence in the Rust community is a blueprint wipe on the first Thursday of the month, aligned with Facepunch forced updates, and a map-only wipe on other Thursdays if you prefer a faster loop. Whatever you choose, publish it: a pinned Discord announcement, a line in the server description, and an in-game message one day before. Servers that wipe on a predictable schedule build a returning population; servers that wipe randomly do not.

Oxide (uMod) plugins without the lag

Oxide turns a vanilla server into a configurable one, and every plugin costs tick time. Install it, then add plugins one at a time and watch the server profiler (Profiler command or perf output in console). Start with a small core set: a queue plugin for wipe day, an auto-restart scheduler, better chat formatting, and a raid or playtime tracker if your rules need it. Avoid stacks of overlapping plugins, because hooks multiply: a plugin hooking every entity spawn runs thousands of times per minute on a busy map.

• Install Oxide, then drop plugins into /oxide/plugins.
• Load config-heavy plugins one at a time and check frame time after each.
• Remove plugins you do not use - an idle plugin still registers hooks.
• Back up /oxide alongside your world folder every night.

Anti-cheat and performance protection

Rust is a competitive game, so you need server-side validation: keep EAC enabled, run a solid anti-cheat plugin for the common exploits, and never trust client positions blindly. On the network side, filter volumetric attacks before they reach the process, because a boot during a raid night is how communities die. Combine that with scheduled restarts during low-population hours and nightly world backups, and your server will keep its population through the wipe cycle.