Server Setup

How to Set Up a Rust Server: Step-by-Step (2026)

Updated July 16, 2026·4 min read

Running your own Rust server gives you full control – your rules, your wipe schedule, your plugins, your community. The catch is that a fresh RustDedicated install is bare-bones: no gather boosts, no kits, no shop, no anti-cheat helpers. This guide walks you through a clean setup from SteamCMD to your first connected player, then points you at the config and mod steps that turn a vanilla box into a real server.

In a hurry? A premade Rust setup ships the config, plugins, and loot tables already dialed in – you drop the files into your host and launch the same day. This guide is the do-it-yourself path.

What you need before you start

  • A machine or rented server: Rust is RAM-hungry. Budget roughly 6–8 GB of RAM for a small map and more as your world size and player count grow.
  • A strong single-thread CPU – Rust leans hard on one core, so single-thread performance matters more than core count.
  • SteamCMD, Valve’s command-line installer, to download and update the server files.
  • Open ports: 28015/UDP (game), 28016/TCP (RCON), and 28082 if you want the Rust+ companion app.

Not sure what hardware to rent? Read how to pick cheap Rust server hosting before you commit to a plan.

Install the server with SteamCMD

The Rust dedicated server is Steam app 258550. Install SteamCMD, then pull the server files into a folder:

steamcmd +force_install_dir ./rust-server +login anonymous +app_update 258550 validate +quit

Re-run that exact command whenever you need to update – Rust ships forced updates on the first Thursday of each month, and an out-of-date server won’t accept players.

Set your startup parameters

Rust reads most of its boot settings from the launch command. Create a start script (a .bat on Windows or .sh on Linux) so you can relaunch consistently:

./RustDedicated -batchmode +server.identity "myserver" \
  +server.hostname "My Rust Server | Weekly Wipes" \
  +server.port 28015 +server.maxplayers 100 \
  +server.worldsize 3500 +server.seed 12345 \
  +server.saveinterval 300 \
  +rcon.web 1 +rcon.port 28016 +rcon.password "CHANGE_ME"
  • server.identity names the save folder – everything for this server lives under server/myserver/.
  • server.worldsize (1000–6000) and server.seed together define the map. Change either and you generate a new map – so keep them fixed between wipes.
  • server.maxplayers is your slot count; don’t set it higher than your hardware can hold.
  • rcon.password protects remote admin – set a strong one and never share it.

First boot and connecting

Run the start script and wait for the console to print Server startup complete – the first map generation can take a few minutes. To join, open the game console with F1 and connect directly:

client.connect YOUR_SERVER_IP:28015

Grant yourself admin from the server console (or RCON) with your Steam ID so you can spawn items and moderate:

ownerid YOUR_STEAM_ID "YourName" "owner"

Configure server.cfg

Persistent settings live in server/<identity>/cfg/server.cfg, which runs on every boot. This is where you set the description, banner image, and moderation defaults. For the full list of convars worth changing – plus gather rates, loot, and performance – follow the Rust server config guide.

Add a mod framework (Oxide or Carbon)

Vanilla Rust has no built-in gather multipliers, kits, shops, or ranks – those all come from plugins, and plugins need a mod framework. Your two choices are Oxide/uMod and Carbon. We compare them in detail in Oxide vs Carbon; install one, drop plugins into its plugins folder, and restart.

This is where most first-time owners stall for days – sourcing plugins, matching versions, and writing loot tables by hand. A premade setup gives you a tested plugin bundle and configs that already work together.

Wipes and going live

A wipe resets the map (and optionally blueprints) to give everyone a fresh start. Facepunch forces a map wipe on the first Thursday of each month with the update; many servers also wipe weekly or biweekly to stay active. Announce your schedule in your server.hostname and server description so players know what to expect.

Once it’s stable, list your server on the Rust server browser and community sites, set up wipe announcements, and you’re live. If you’d rather skip the plumbing, our ready-to-deploy setups get you from empty box to launch-ready in an afternoon.

FAQ

How much RAM does a Rust server need?
Plan for roughly 6–8 GB for a small map and low player count, scaling up with world size and slots. Large modded servers can use 16 GB or more.
Is it free to run a Rust server?
The server software is free. You pay for the hardware it runs on – either your own machine and bandwidth, or a rented host, which for a small server is usually a few dollars a month.
Do I need Oxide or Carbon to run a server?
No – a vanilla server runs without them. But you need one of them for any plugins: gather rates, kits, shops, ranks, and custom loot are all plugin features.

Skip the setup

Rather not build it all by hand? Our premade Rust setups ship the configs, plugins, and loot tables already dialed in – drop them into your host and launch the same day.

Keep reading