Starting the process is the easy part. Figuring out how to make a Rust server that people log back into on a Tuesday night, three weeks after they first joined, is a different job entirely. Most community servers die inside a month, and it's almost never the hardware. It's that the wipe cadence was random, or an admin was asleep at the wheel while a cheater cleared the whole map. So we'll build one that lasts, starting at the config file and ending with the human stuff that keeps a server full.
Getting the server running
Rust runs on RustDedicated, the standalone server binary Facepunch ships through SteamCMD (app ID 258550). On Linux you pull it with steamcmd, point it at an install directory, and launch with a startup line that sets your ports and server identity. Two ports matter most: the game port (28015 UDP by default) and the RCON port (28016), plus a query port for the server browser. The same binary runs on Windows, but Linux is the sane pick for anything persistent. It doesn't fight you on updates and it sips RAM by comparison.
Budget that RAM properly. A vanilla server at 3500 worldsize with 50 players wants 8 to 12 GB, and it climbs fast once you crank the map or stack heavy plugins. Rust is one of the most demanding games to self-host. Undersized hardware shows up as rubber-banding and 20-second spawn times at exactly the moment the server is busiest and you most want it smooth. If you'd rather skip the SteamCMD dance and the update babysitting, our Rust server hosting hands you instant setup with the binary and Oxide already wired up, plus DDoS protection a home connection can't touch.
The server.cfg convars that define your server
Your identity folder holds server.cfg, and that file is where your server gets its personality. It runs on boot, one convar per line. A handful you'll set on day one:
- server.worldsize: map dimensions in meters. 3000 is small and tight, 4000 is the sweet spot for most communities, and 4500 or higher starts feeling empty unless you're pulling 100-plus players. Keep it between 1000 and 6000. Go bigger and generation gets slow and strange.
- server.seed: the number that decides your map layout. Same seed plus same worldsize gives you the same map every time. When you find a good one, write it down.
- server.maxplayers: your hard cap on concurrent players. Set it to what the hardware and map can actually hold, not what you'd like them to.
- server.hostname: the name in the browser. Put your wipe schedule right in it, like "[EU] 2x Weekly | Wipes Thursday". People filter by exactly this.
- server.description: supports \n for line breaks. Spell out gather rates, wipe day, and rules here so nobody has to ask in chat.
- server.tickrate: leave it at 30 unless you know precisely why you're touching it. Higher isn't free, and your CPU pays the bill.
Here's a gotcha that catches everyone: server.seed and server.worldsize only take effect on a fresh map. Change them mid-wipe and nothing happens until you wipe the map file. New admins burn an hour on this, editing the seed, restarting, editing again, and wondering why the map keeps looking identical.
Oxide and the plugins worth running
Vanilla Rust gives you almost nothing for admin tooling, which is why nearly every community server runs Oxide, the modding framework maintained these days as uMod. You install it by dropping the Oxide files over your server install, restarting, and checking that an oxide/ folder appears. Plugins are single .cs files you drop into oxide/plugins/, and they hot-load without a restart, which is genuinely handy when you're tuning things live.
Fight the urge to install thirty plugins on launch. A bloated plugin folder is the number one source of mystery lag and load-order conflicts nobody can trace. Start lean:
- AdminRadar plus a maintained anti-cheat companion for catching the obvious stuff mid-game.
- PlaytimeTracker or similar, so you can actually see who your regulars are versus one-night visitors.
- A kit or shop plugin if you're running modded. On a plain 2x server, keep economy plugins minimal. People showed up for Rust, not a storefront.
- Discord logging (DiscordCore-based plugins work well) so F7 reports and bans land in a channel you're already staring at anyway.
My honest take: run the fewest plugins that solve a real problem you've actually hit. Every plugin is code you now maintain through every forced wipe, and Facepunch breaks the modding API on the first Thursday of most months like clockwork. If a plugin has gone six months without an update, assume it'll break and find a maintained replacement before it strands you on wipe day.
Admin commands you'll use constantly
Get comfortable in the F1 console and RCON, because you'll live in both. The ones you'll reach for daily:
- ownerid STEAMID "name" "reason" followed by server.writecfg to make someone a permanent owner-level admin that survives restarts. Skip the writecfg and it quietly vanishes on the next reboot.
- moderatorid STEAMID for trusted helpers who need kick and ban but not the keys to the whole server.
- global.ban STEAMID "reason" and global.kick for the obvious calls.
- global.teleport2me STEAMID to yank a suspected cheater over to you for a closer look before you decide.
- server.save before any risky change. It forces a save so a crash won't roll back an hour of progress.
Set RCON up properly with a strong rcon.password, and you can moderate from a web panel or a Discord bot without alt-tabbing back into the game. When the server's packed and someone is blatantly flying over a raid, banning in 15 seconds instead of two minutes is the difference between keeping the lobby and watching it empty.
Wipe cadence: the thing that makes or breaks the server
Here's the part nobody wants to hear. Your wipe schedule matters more than your plugins, your map, and your rules combined. Rust is a game of fresh starts, and a community lives or dies on whether players can trust the rhythm. The standard is a map wipe every Thursday, lined up with Facepunch's forced-update wipe on the first Thursday of the month, a blueprint wipe monthly, and map-only wipes on the weeks in between.
Pick a schedule and never surprise anyone with it. Announce it in the hostname, the description, and a pinned Discord post. A player deciding whether to raid tonight or bank resources needs to know if the map resets in two days or nine. Move your wipe day on a whim and you'll watch regulars drift off to a server that respects their time. Weekly is the most popular for good reason. Biweekly suits a slower, more building-focused crowd. Daily wipes are a niche grind that burns most people out inside a week.
Automate the whole thing. A wipe means deleting the map save, plus the blueprint data on a BP week, then letting the world regenerate. Set a cron job or use your host's scheduled-task feature so it fires at the same hour every week whether you're awake or not. Consistency you have to remember to enforce by hand isn't consistency, it's a coin flip.
Moderation is a staffing problem, not a plugin
The second server-killer, right behind wipe chaos, is unmoderated cheating. No anti-cheat catches everything, and Rust's cheating scene is relentless and well-funded. What keeps honest players around is knowing that when they hit F7 to report a flyhacker, a human looks within minutes. That means admins spread across timezones, a clean report pipeline into Discord, and a no-tolerance ban policy you enforce on your own friends too, not just strangers.
Build a small, trusted admin team before you open the doors, not after the first exodus. Give them moderatorid access, a private channel, and a written standard for what earns a ban so calls stay consistent between staff. The servers that survive their first month are the ones where the owner treated moderation as a recurring shift instead of a one-time setup step.
Once the config and cadence are dialed in, the rest is upkeep and community. If you're still weighing self-hosting against a managed box, our guide on how to choose game server hosting lays out the real tradeoffs, and our game server hosting plans in Frankfurt, London, and Gravelines keep European ping low with the kind of DDoS protection a public Rust server genuinely needs. Get the wipe schedule right and the moderation staffed, and you'll have what most Rust servers never manage: regulars who keep showing back up.