acidnodes
Rust server hosting — live

Rust server hosting where the map is yours to choose.

On Rust, the map IS the product decision — and here the seed and world size are panel fields, not a support ticket. We measured a live server before pricing it: a 4.9 GB working set on a 3000 map, peaking at 6.3 GB, zero memory pressure at an 8 GB cap. So the floor is 8 GB at $22 on a Ryzen 9 9950X, with 128 server settings as labeled fields and the Carbon mod loader ready for the whole Oxide plugin ecosystem.

See the exact machine

Rust dedicated server hosting price: from $22/mo · 8 GB dedicated RAM · AMD Ryzen 9 9950X · never oversold

From the team behind GamesOMG — the Rust guides and tools players already use. Play more. Configure less.

We asked the game itself
what a Rust server can do.

The settings, the memory floor and the mod loader were all measured on our own node — not copied off a wiki.

01 — measured, not guessed

4.9 GB working set. 8 GB floor.

We read the memory off a live server the way you are supposed to — the unreclaimable working set from the kernel, not a dashboard number padded with cache. 4.9 GB on a 3000 map, 6.3 GB peak, zero pressure events at 8 GB. A 6 GB plan would have looked cheaper and throttled from day one, so we do not sell one. Bigger map? The 12 GB rung exists because map size, not player count, is what grows Rust.

02 — the map is the product

Seed, size, and a fresh world when YOU say.

Rust servers live and die by their map. Seed and world size are labeled panel fields here — new wipe, new seed, done. The panel is honest about the sharp edge: changing either regenerates the world, and it says so before you do it. The other 126 settings — player cap, PvE mode, damage multipliers, decay, populations — came from asking the running game to enumerate its own convars, descriptions and defaults included.

03 — plugins without the trap

Carbon, because Oxide breaks on shared images.

Oxide patches a DLL inside the game install — on any host that shares game files between servers, that patch silently vanishes on the next rebuild and your "modded" server reverts to vanilla. We ship Carbon instead: it touches nothing in the game tree, hot-loads .cs plugins without a restart, and runs Oxide plugins unmodified. Same ecosystem, none of the quiet reverts. And your SteamID lands in users.cfg as owner — you are admin on the thing you pay for.

How much RAM does a Rust server need?

We measured a live Rust server on a 3000-size map: a 4.9 GB unreclaimable working set, peaking at 6.3 GB, with zero memory-pressure events at an 8 GB cap — so 8 GB is a real floor, not a teaser. The thing that grows Rust memory is the map, not the player count: a 4000-size world or a serious Carbon plugin stack belongs on 12 GB, and 16–24 GB buys a big map plus a second game running beside it from the same pool.

Bored of Rust in three months? Your world still waits. Switch this server to any other game your plan has the RAM for — free, instantly, as often as you like — and your Rust world stays exactly as you left it. Come back next year and it is still there, not reinstalled. Most hosts “switch” by wiping and reinstalling; a few charge you a stored slot for every world you want to keep. We keep them all, because each game writes to its own save area on your volume.

And if you would rather not choose: your RAM is a pool. Size up once and run Rust and something else side by side on the same plan, with no second bill.

Straight answers, no pitch

How much does Rust server hosting cost?

From $22/mo for 8 GB, $32 for 12 GB, $41 for 16 GB or $59 for 24 GB — guaranteed dedicated RAM, no slot pricing, no setup fee. You set the player cap yourself and the price does not move.

How much RAM does a Rust server actually need?

We measured a live server on a 3000-size map: a 4.9 GB working set, peaking at 6.3 GB, with zero memory-pressure events at an 8 GB cap. That is why the floor is 8 GB — a 6 GB plan would have run at its ceiling from day one, and we do not sell those. Map size is the real lever: a 4000 map wants the 12 GB rung.

Can I change the map — seed, size, all of it?

Yes, and on Rust that IS the server: seed and world size are panel fields, so every wipe can be a genuinely new map. One honest warning the panel repeats: changing seed or size regenerates the world — your old map is gone the moment the new one boots. Name, player cap and the rest change without touching the world.

Can I run plugins — Oxide, uMod, Carbon?

Yes. Your server ships with the Carbon mod loader available — flip mods on in the panel, drop .cs plugins into the carbon/plugins folder (the Files tab links you straight to it), and Carbon hot-loads them without a restart. Carbon runs Oxide/uMod plugins unmodified, so the whole existing ecosystem works. We proved the load path with our own probe plugin before shipping it.

Am I actually admin on my own server?

Yes — put your SteamID64 in the panel and it lands in users.cfg as owner before every boot. Worth saying plainly because vanilla Rust ships that file empty: on a lot of hosts you are renting a server you cannot even admin. RCON works too — the panel generates the password and wires the port, and tools like RustAdmin and BattleMetrics speak to it directly.

How do wipes work here?

You wipe when you want to: change the seed (or keep it and just delete the map file from the Files tab) and restart. There is no forced wipe schedule from us — your server, your calendar. Facepunch forces a map wipe on the first Thursday of each month only when the game updates require it, which is the same on every host.

Do you back up my server?

Yes — nightly, automatically, off-site on a separate network. One-click restore or download from the panel, plus pre-update snapshots before game patches.

Where are the servers?

NA East (Montreal) — AMD Ryzen 9 9950X, NVMe storage, DDoS-protected network, direct game and query ports. Every plan page measures your real ping in your browser before you buy.