How to Host a Rust Dedicated Server in 2026
I've been running Rust servers for long enough to know that most "how to host Rust" guides skip the parts that actually bite you once the server is live. So this is the version I'd hand a friend who asked me how to do it properly in 2026 – what the game actually needs, where people waste money, and the bits of the panel you'll end up living in.
Why bother hosting your own?
Playing on other people's servers is fine until it isn't. You want a specific wipe day, you want your own rules, you want Oxide plugins the other admins won't touch, or you just want a private spot for your group where nobody's blasting slurs over global chat. Self-hosting gives you that. It also means you're the one who has to keep the thing alive, which is the trade-off nobody mentions in the sales pitch.
A few honest reasons people pull the trigger:
- You want a wipe schedule that fits your group, not Facepunch's officials.
- You want to run Oxide/uMod (or Carbon) plugins without asking permission.
- You want a whitelist and a Discord that actually feels like a community.
- You're tired of 200ms pings on random EU community boxes.
The hardware reality check
Rust is one of the most RAM-hungry games you can host. Roughly 8–16 GB covers most community servers comfortably; heavily modded boxes or anything pushing 200+ players can go higher, and entity buildup through a wipe cycle makes things worse the longer you go without wiping. If you've ever watched a Rust server's memory climb day by day until it chokes, that's what you're budgeting against – not just peak player count.
CPU matters nearly as much as RAM, and not in the way people expect. Rust's server is mostly single-threaded, so clock speed and per-core performance beat core count every time. A modern high-clock Ryzen will run circles around a 32-core cloud VM that looks impressive on paper. Network matters too – you want a host with real DDoS filtering, because Rust servers get hit, full stop.
Storage is the least dramatic of the three. An NVMe SSD, 20-ish GB free, you're done.
Home, VPS, or managed?
Self-hosting on your home PC works for a 4-player private server and nothing else. Your upload pipe will cap you, your IP is exposed, your ISP won't thank you, and a single DDoS ruins your evening. I don't recommend it unless you genuinely just want your mates to raid each other for a weekend.
A VPS or dedicated box gives you full control and usually worse value than people think. You're installing SteamCMD, writing start scripts, managing updates, configuring the firewall, and – when something breaks at 2am mid-wipe – you're the one fixing it. If you enjoy Linux admin, go for it. If you don't, you'll hate it by week three.
Managed game server hosting is what most people actually want. You get a panel, one-click mod installs, backups handled for you, DDoS protection baked in, and a support team you can ping when something's misbehaving. It's the boring answer, but it's the right one unless you specifically want the sysadmin hobby.
How to pick a host (without getting burned)
Forget the headline price. What matters is whether the plan gives you enough RAM to actually run Rust without the server gasping through the back half of a wipe, whether DDoS protection is actually included, how quickly support actually replies when you open a ticket on a Sunday night, and whether the panel lets you install Oxide or Carbon without SSHing into anything. If those four things are solid, price sorts itself out. If any one of them is weak, the "cheap" host ends up being the most expensive mistake of your month.
Getting set up on LOW.MS
I'll walk through it on our panel because that's what I know. Head to LOW.MS Rust hosting, pick a plan with plenty of RAM, and check out. Your server is provisioned automatically – you'll get login details for control.low.ms within a minute or two.
Once you're in the panel, the bits you'll touch most often are:
- Service Settings – server name, description, slots, the basics.
- Configuration Files –
server.cfgand friends when you want to tune things manually. - Mod Manager – this is how you install Oxide/uMod. One click, done.
- File Manager – for dropping plugin
.csfiles intooxide/pluginsand editing configs. - Web Console – live server console in your browser for commands and log tailing.
- Steam Update – pull Facepunch's monthly update on forced-wipe day.
Give it a name, set your max slots, hit start, and you're live. When you want to join, fire up Rust, press F1, type client.connect <your-ip>:28015 and you're in. Our walkthrough over at How to connect to a Rust server via IP covers the other join methods if the console one isn't your thing.
Installing mods
Rust modding lives at umod.org (still called Oxide by half the community and uMod by the other half – same thing). On LOW.MS you install it through Mod Manager – pick Oxide, click install, restart. Plugin files themselves are just .cs files, and you drop them into oxide/plugins with File Manager; the server picks them up on the fly.
Worth knowing: Carbon is an Oxide-compatible alternative that's been gaining ground, and most uMod plugins work on it unchanged – if you hit a performance wall with Oxide it's worth a look. For a starting plugin list I'd actually recommend, see Top Rust Oxide Plugins.
Wipe cadence
Forced wipe is the first Thursday of every month – Facepunch pushes the monthly patch and your map has to reset whether you like it or not. Between those, you choose. Weekly wipes suit PvP-first servers where people want fast raids and no mega-bases. Fortnightly is probably the sweet spot for most communities. Monthly-only (so, just the forced wipe) is where builders and PvE folk live.
One thing that catches new admins out: blueprint wipes. They happen less often – usually quarterly or so – and Facepunch occasionally forces one with a big update whether you planned it or not. Tell your players before it happens or expect angry Discord pings.
Whatever you pick, put it in your server name and description and stick to it. Players leave servers that surprise-wipe them more than they leave servers that wipe too often.
Getting players
A server with nobody on it dies fast. Get listed on BattleMetrics, rust-servers.net, and just-wiped.net – those three cover most of the discovery traffic. Set your server.tags properly (wipe cadence, region, modded/vanilla, rates) because the filters on those sites actually use them, and write a server description that tells people what you are in the first line, not the fifth.
Beyond that: run a Discord, wipe on schedule, deal with cheaters quickly, and be visible in chat. That's most of it. The servers that grow are the ones where the admin is a person, not a silent name in the header.
Where to read next
If you want to skip the research and just get a box running, grab a Rust server on LOW.MS and you'll be in-game inside five minutes.