Ready to play?
Pick your game, choose a plan, and start playing in under 60 seconds. No lag, no excuses.
Woof! Let's go!


Running your own Rust server gives you control over wipes, plugins, player slots, and admin powers you never get on someone else's box. Rust is also one of the most demanding games to host, so getting the specs and the wipe schedule right matters. This guide covers how to host a Rust server in 2026: the hardware that actually moves the needle, how to add Oxide plugins, and how to survive force-wipe day.
Rust is heavier than most survival games. Four things decide whether your server holds up:
For a small vanilla server up to about 50 players, 4 to 8 GB of RAM is a good starting point. A 100-slot server wants 8 to 12 GB. A 100-slot modded server running 30 to 40 Oxide plugins needs 12 to 16 GB in steady state, plus 25 to 35 percent extra headroom for force-wipe day, when fresh maps and a flood of new players spike memory. Buy a bit more RAM than your steady-state number so wipe day does not knock you over.
You have two real options:
Self-host on a VPS or home box. You download SteamCMD, pull the Rust server files, open ports, configure the startup flags, and manage updates and wipes by hand. It is the cheapest in raw dollars and teaches you the most. It also means you are the sysadmin at 2 a.m. on wipe night, and a home connection rarely has the upload headroom or DDoS protection a public server needs.
Rent a managed Rust server. A host gives you a panel, one-click Oxide, automatic updates, scheduled wipes, NVMe storage, and DDoS protection. You trade a little control for a lot less maintenance. For most groups that want to play rather than administer, that is the better trade.
If you go managed, size for the RAM numbers above, confirm NVMe, and check that the host lets you schedule wipes and toggle Oxide without filing a support ticket.
Oxide, now maintained under the uMod project, is what turns vanilla Rust into a kits, shops, clans, and teleport server. On most managed panels the workflow is:
oxide/plugins folder, or install them from the panel's plugin browser.oxide/config, then reload it from the server console with oxide.reload PluginName.Good starting plugins: a kit manager, a teleport or home system, a shop or economy plugin, and a clan or team plugin. Add admin tools like a remove tool and a better chat plugin. Keep the plugin count honest, because every plugin adds RAM and CPU load.
Rust's default game port is 28015 UDP, with 28016 used for RCON (remote admin). If you self-host, forward 28015 UDP. On a managed host these are handled for you.
The settings most servers change first:
server.hostname and server.description: your name and blurb in the server browser.server.maxplayers: your slot cap. Match it to your RAM, not your ambition.server.seed and server.worldsize: the map. A worldsize of 3000 to 4500 suits most communities. Bigger maps need more RAM and CPU.server.tickrate: leave it at the default 30 unless you have a specific reason to change it.Set these in your server.cfg or through the panel, then restart for them to take effect.
Wipes are core to Rust. Facepunch force-wipes the game on the first Thursday of every month, around 19:00 UTC, which invalidates existing maps and drives the biggest wave of returning players. Two things to plan for:
Because the start-of-month surge is so predictable, wipe day is also when an hourly-billed server pays off: spin up extra capacity for the rush, then scale back down once the wave settles.
Hosting a Rust server in 2026 comes down to single-thread CPU speed, enough RAM for your players and plugins, NVMe storage, and a wipe plan that lines up with force-wipe Thursday. If you would rather skip the SteamCMD and port-forwarding grind, rent a managed Rust server on BruceNode with one-click Oxide, scheduled wipes, NVMe storage, and DDoS protection on every plan. Use code BRUCE20 for 20% off your first month, and you can have a server live and wiped before the next first Thursday.