Rust servers.
Ask before you build.

Start from your map size, not your player count. We measured a Rust server with Carbon loaded and nobody connected: a 3000 map idles at 5.0 GB, a 4000 map at 6.65 GB and a 4500 map at 8.41 GB. That is the floor before a single player joins or a single base is built, and it is why map size drives the plan more than head count does. So pick the map you want, leave room on top for players and bases, and size for your busiest hour — usually the first hour after a force wipe. A heavy plugin stack pushes you up one size.

More than most hosts imply, and it depends almost entirely on your map size. Measured on our own hardware with Carbon loaded and zero players: 3000 map 5.0 GB, 4000 map 6.65 GB, 4500 map 8.41 GB. Memory grows faster than the map does — going from 4000 to 4500 costs nearly double what 3000 to 4000 costs, because bigger maps carry more monuments and baseline entities. Players and the bases they build sit on top of that floor. If a plan's RAM is close to your map's floor, you have nothing left for the server actually filling up.

No. Every feature is on every plan, including Solo: the wipe schedule, the cadence tag, your choice of Oxide, Carbon or vanilla, the import tool, the browser console, file manager and SFTP. Bigger plans get more RAM, more CPU cores, room for a bigger map, more disk and more backup slots. Nothing is locked behind a tier.

As soon as payment clears, usually within five to twelve minutes, depending on how big a map you pick. Every server starts on vanilla; switch to Oxide or Carbon from Server Settings and restart.

Yes, up or down, from the panel. Your map, plugins and player data stay where they are. Upgrades are prorated and charged when they apply; downgrades take effect at your next renewal.

The player range is your slot cap, so anyone over it waits in the queue. If you hit the cap every wipe, that is your sign to move up a size.

Zerg is our biggest plan, at up to 350 players. Every plan is a fixed price with no custom quotes, so if you're outgrowing Zerg, the usual move is a second server on its own plan.

Yes. Each server is its own plan, all managed from one dashboard.

Rust leans hard on one fast CPU core, so we buy high-clock chips: AMD Ryzen 9 7950X. Memory is dedicated DDR5 that is not shared or oversold, and storage is NVMe.

London, Frankfurt, Helsinki, Virginia, Dallas and Sydney. DDoS filtering is on in every location, tuned for game traffic.

Facepunch ships a new build on the first Thursday at 19:00 London time and every server in the game wipes. In order:

1. 01 Facepunch releases the force-wipe build
2. 02 Your server installs it — nobody can join until it does
3. 03 Oxide or Carbon rebuilds; plugins pinned to the old version stop loading
4. 04 Take a backup before anything is deleted
5. 05 The map goes: six files, all prefixed proceduralmap.
6. 06 Blueprints, if you want them gone: one database plus its -wal file
7. 07 Server restarts and generates the new map

For a force wipe, yes for now: you update and wipe the server yourself. Your scheduled wipe timer and cadence tag keep working without you, and the automatic run is what we are building next.

Facepunch force-wipes every server on the first Thursday of the month, usually at 7pm UK time (2pm in New York). Our force-wipe calendar knows the schedule, so your monthly wipe lines up without you counting weeks.

Yes, in game. Your wipe schedule writes Rust's own wipe-timer convars, so players see the countdown to your next wipe from inside the server. Discord posting is not built yet.

Yes. Pick weekly, fortnightly or monthly and the day and hour. That one setting drives both the in-game countdown and the cadence tag players filter by in the server browser. Running the wipe itself is still up to you, and our wipe files guide lists exactly what to delete.

Check the console — Oxide and Carbon name the plugin that failed to load. Disable it from the file manager, or restore the backup you took before the update, and update it when the author ships a build for the new version. An automatic check is on our list; it does not exist yet.

Only if you took a backup first, so take one from the Backups tab before every wipe. Restoring it is one click. Plans keep up to 3, 7, 14 or 30 backups.

Either, on every plan. Servers start on vanilla: pick Oxide or Carbon in Server Settings and restart. Each keeps its plugins in its own folder (oxide/plugins or carbon/plugins), so if you switch later, move your plugins and their data across yourself. Most uMod plugins run on Carbon too.

Upload the plugin's .cs file to oxide/plugins (or carbon/plugins) with the file manager or SFTP, and the framework loads it. A one-click installer is not built yet.

Yes. Upload them like any other plugin. The licence stays with you.

Our panel doesn't show plugin timings yet. On Oxide, the oxide.plugins console command lists every loaded plugin with the hook time it has used, which is the quickest way to find the heavy one.

Yes. SFTP and a browser file manager for every file and server.cfg, plus a live browser console.

Procedural maps at the size and seed you choose, set from your dashboard. Custom map files by URL are not in the dashboard yet: open a ticket with the map's download link and we set it for you. Each plan has a recommended map size for smooth play; bigger maps are the usual reason to go up a size.

Not on a copy of your live server — we do not offer that, and Rust's staging branch cannot be selected through the panel. What you can do is take a backup first, make the change, and restore if it goes wrong.

Not yet, and we would rather say so. Companion pairing returns an error we have not got to the bottom of. We will update this answer the day it works.

Nearly always a delete pattern that misses a file. Rust keeps rolling map backups at .sav.1 and .sav.2, so a script matching *.sav leaves older copies of the world on disk. Match on the proceduralmap. prefix instead. The other one: every SQLite file has a -wal sibling, and SQLite's own documentation says a database and its journal must be kept together. Delete both. We confirmed both on a live server rather than trusting the defaults that ship with the egg.

Facepunch's Community Server and Hosting Guidelines allow things like VIP or subscriptions, donations, cosmetics, server currency and ads. What you can't do is hand out Facepunch DLC or skins to players who haven't bought them, and your server has to be fairly labelled. Read the guidelines yourself before you set up a store; this isn't legal advice.

No. Rust is a trademark of Facepunch Studios Ltd. We're an independent host and not affiliated with or endorsed by Facepunch.

Yes. The import tool is in every server's dashboard, Solo included, and costs nothing.

Whatever you pick from your old server: files, plugins and their configs, player data and the map. It shows you the old server first, then copies the folders you choose. You do the import yourself from the Import tab.

No. The importer only reads from your old server, so it keeps running until you move your players across.

Your current host's SFTP details: address, port, username, and a password or key.

Not if you copy the save folder (server/<identity>/) with everything else. Then they connect to the new address, or nothing changes for them at all if you point your own domain at the server.

Monthly, from the day you deploy. No setup fee and no contract.

From the panel, any time. Your server keeps running to the end of the month you've paid for.

Yes, within 7 days. Tell us inside 7 days of your first payment and we refund it in full, no reason needed.

Card and PayPal. Prices are in GBP, with no VAT to add.

Discord for quick questions and wipe notes, tickets for anything to do with billing or your account. Same queue on every plan. Most tickets get a first reply within a few hours.

Not with tools yet. Moderation tools are on our list but not built, so today it's Rust's own admin commands and whatever moderation plugins you run. You can give each of your admins their own sub-user login.

Yes. Add them as sub-users at View, Operator, Manager or Admin level. They get their own login, and you choose how much of the server they can touch.

The team behind Connect Hosting, an official BeamMP partner. Same people, same infrastructure, a host built just for Rust.