How to Make a Rust Server, Step by Step

Downloading the server files with SteamCMD

SteamCMD is Valve's command-line tool for downloading dedicated server files. Rust's server app ID is 258550.

On Linux (Ubuntu or Debian):

1. Install SteamCMD from your distribution's repository or Valve's official archive. We recommend running the server as a separate user rather than root.
2. Download the Rust server files:

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

On Windows:

1. Download steamcmd.zip from Valve's site and extract it to a folder such as C:\steamcmd.
2. Run this in a command prompt:

   steamcmd.exe +force_install_dir C:\rust\server +login anonymous +app_update 258550 validate +quit
   

+force_install_dir must come before +login. Run the same command after every Rust update to keep the server files current.

Starting the server and basic settings

Rust server settings are passed as parameters in the launch command. On Linux, create a start.sh file in the server folder:

#!/bin/sh
./RustDedicated -batchmode \
  +server.port 28015 \
  +server.level "Procedural Map" \
  +server.seed 12345 \
  +server.worldsize 3500 \
  +server.maxplayers 50 \
  +server.hostname "Your server name" \
  +server.identity "myserver" \
  +rcon.port 28016 \
  +rcon.password "a-strong-password" \
  +rcon.web 1 \
  +app.port 28082

On Windows, put the same parameters in a start.bat file with RustDedicated.exe. The settings that matter most:

• server.hostname: the name in the server browser.
• server.worldsize and server.seed: map size and the number that generates the map. The same seed and size always produce the same map.
• server.maxplayers: the player limit.
• server.identity: the name of the server's save folder. The map, player data and config live under server/<identity>.
• rcon.password: the remote admin password. Always use a strong one.

The map is generated on first start, which takes a few minutes. When the console shows "Server startup complete", the server is ready.

Match the map size to your player count

On a 50-player server, a 4500 map makes it hard for players to find each other and wastes RAM. On a 200-player server, a 3000 map fills up fast. 2500–3000 is a good start for friends, and 3500–4000 for community servers. Load custom maps you have designed or bought with server.levelurl.

Make yourself an admin

Find your 17-digit SteamID64 on your Steam profile and type this in the server console:

ownerid 76561198000000000 "YourName"
server.writecfg

server.writecfg saves the permission permanently. Reconnect to the game and you can use admin commands.

Ports and the firewall

A Rust server uses these ports by default:

• 28015 UDP: the game port players connect to.
• 28016 TCP: the RCON port for remote admin tools.
• 28082 TCP: the app port for the Rust+ companion app.

With ufw on Linux:

sudo ufw allow 28015/udp
sudo ufw allow 28082/tcp

Rather than opening the RCON port to everyone, allow only your own IP. Rust servers are frequent attack targets around wipe day; our guide What is a DDoS attack? explains why protection in front of your server matters.

Installing plugins with Oxide or Carbon

Plugins are what set your server apart from vanilla Rust: starter kits, teleports, clan systems, economies or changed gather rates. You use one of two frameworks:

• Oxide (uMod): The long-established framework. Download the Rust build for your operating system from umod.org, extract it into the server folder and overwrite the existing files. Plugins go into oxide/plugins as .cs files and load without restarting the server.
• Carbon: A newer, performance-focused framework. It runs most Oxide plugins unchanged with lower memory and CPU overhead. Plugins go into carbon/plugins.

Don't install both; pick one. After every Rust update you also need to update Oxide or Carbon, or plugins won't load.

Under Facepunch's rules, servers whose plugins change gather rates, kits or game rules must be listed in the Modded tab. If you only use admin plugins, you can stay in the Community tab.

The wipe schedule and updates

Facepunch releases a mandatory update on the first Thursday of every month, and with it the map is reset on every server (the forced wipe). Whether blueprints are wiped is usually up to the server owner. We recommend this routine on wipe day:

1. Stop the server and back up your save folder.
2. Run the SteamCMD command again to update the server files.
3. Install the new version of Oxide or Carbon.
4. Change server.seed or delete the map file in the save folder to reset the map.
5. Start the server and check the console that plugins load without errors.

Wipe day is both your busiest and your most critical day. Getting the update out fast is the easiest way to keep players.

Connecting and keeping it smooth

Players press F1 in game to open the console and connect with:

client.connect server-ip:28015

Once your server has registered, players can also find it by name in the server browser.

As the wipe goes on, every wall, door and box on the map adds load as an entity. To keep the server smooth until the end of the wipe:

• Restart once a day. A Rust server uses more and more memory the longer it runs.
• Keep the save interval sensible. Setting server.saveinterval too short adds needless load.
• Leave decay on. Letting abandoned bases decay keeps the entity count under control.
• Choose plugins by measuring. Oxide and Carbon can report how much time each plugin takes; replace the expensive one with a lighter alternative.

Renting a Rust server

Setting up a server yourself teaches you a lot, but Rust's RAM needs and the load on wipe day quickly push home connections and PCs to their limits. Nodesty's Rust server hosting runs in Frankfurt on the Ryzen 9 9950X, which boosts to 5.7 GHz, with plans from 8 GB of RAM, NVMe storage and L3–L7 DDoS protection. Choose Rust during installation and the server files come preinstalled. For other games, see our guides on how to make a Minecraft server and how to make a FiveM server.