How to Make a Rust Server (2026 Guide)

Rust has no co-op mode: every multiplayer world, from a small group of friends to a 200 player monthly, runs on a dedicated server. The server software is free from Facepunch and runs on Windows and Linux. This guide walks through installing it, choosing your map, opening the right ports and getting friends in. At the end there is a quicker option if you would rather skip the setup.

Short on time? A hosted Rust server is live in about 60 seconds with its own address, no SteamCMD and no port forwarding. How to host a Rust server walks through it step by step.

What you need

• A machine that stays on while people play. A spare PC or a Linux box both work. Rust bases decay while the server runs, so in practice this means 24/7 for the whole wipe.
• At least 8 GB of RAM free for a small map, and 12 GB or more for a standard 4000 size map. Facepunch lists 12 GB as the baseline.
• Around 15 GB of free disk space, ideally on an SSD.
• A fast CPU. Rust leans on single core speed more than core count.
• Access to your router, so players outside your home can connect.

Not sure how much memory to give it? Read how much RAM a game server needs.

Step 1: Install SteamCMD

SteamCMD is Valve's command line tool for downloading dedicated servers.

• Windows: download the SteamCMD zip from Valve, extract it to a folder such as C:\steamcmd and run steamcmd.exe once so it updates itself.
• Linux (Debian or Ubuntu): install the steamcmd package from your distribution, or download Valve's Linux tarball and run ./steamcmd.sh.

Step 2: Download the Rust server

The Rust dedicated server is app ID 258550, and it downloads without a Steam account:

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

On Linux, use a path like ~/rust-server instead. Run the same command again whenever Rust updates, because players cannot join a server on an older version. On a hosted server, a restart after the update does this for you.

Step 3: Create a start script

Rust is configured mostly through launch options. On Windows, create start.bat in the server folder:

RustDedicated.exe -batchmode +server.port 28015 +server.queryport 28017 +server.level "Procedural Map" +server.seed 1234 +server.worldsize 4000 +server.maxplayers 50 +server.hostname "My Rust Server" +server.identity "myserver" +rcon.port 28016 +rcon.password "change-this" +rcon.web 1 -logfile server.log

On Linux, the same options work with ./RustDedicated at the start of the line. What the important ones do:

• -batchmode: runs without a window, which every dedicated server needs.
• +server.seed and +server.worldsize: together they decide the map. World size ranges from 1000 to 6000. 3000 suits a small group, 4000 to 4500 is the classic community size.
• +server.maxplayers: the player cap.
• +server.identity: the folder name your save and config live in, under server/myserver/.
• +rcon.password: always change it. RCON gives full control of the server.

The first start takes several minutes while the map generates. The server is ready when the console shows Server startup complete.

Step 4: Settings in server.cfg

Anything you would type in the server console can also go in server/myserver/cfg/server.cfg, one setting per line without the +. Common additions:

server.description "Weekly wipe, 2x gather, active admins"
server.url "https://example.com"
server.headerimage "https://example.com/banner.png"

Restart the server to apply the file.

Step 5: Make yourself an admin

Find your SteamID64 (your Steam profile URL or any SteamID lookup site shows it), then type this in the server console:

ownerid 76561198000000000 "YourName"
server.writecfg

server.writecfg saves the change to users.cfg so it survives restarts. Reconnect and you have admin powers. Use moderatorid for moderators.

Step 6: Open the ports

Players at home can join on your local IP. For everyone else, forward these ports on your router to the server's local IP address:

If you use the Rust+ companion app, its port (app.port, 28082 by default) needs TCP forwarded too. Allow RustDedicated through your firewall as well. Our port forwarding guide covers the router side step by step. If your internet provider uses CGNAT, forwarding will not work at all, and a hosted server with its own public address is the simplest way around it.

Step 7: How friends connect

Send friends your public IP (search "what is my IP"). They launch Rust, press F1 to open the console and type:

client.connect 203.0.113.10:28015

using your IP instead of the example. Once the server has been up for a few minutes it also appears in the Community tab of the server browser, or the Modded tab if you install plugins, where people can search for it by name and add it to Favorites.

Adding Oxide or Carbon plugins

Rust plugins are server side, so players never install anything. Two frameworks load them:

• Oxide (uMod): download the Rust build from umod.org and extract it over your server folder, replacing files. Plugins go in oxide/plugins.
• Carbon: a newer, performance focused framework that runs most Oxide plugins. Install it from carbonmod.gg.

Both need reinstalling after every Rust update, because the update overwrites their files. Reload a plugin without restarting with oxide.reload PluginName.

Wiping

Facepunch releases a big update on the first Thursday of each month, and old maps do not work after it, so every server wipes then. To wipe by hand, stop the server and delete the .map and .sav files in server/myserver/. To also wipe blueprints, delete the player.blueprints database files in the same folder. Change the seed at the same time if you want a fresh map. How to wipe a Rust server lists every file for map, blueprint and full wipes.

Common problems

• Server does not show in the browser: give it a few minutes, then check the query port is forwarded as UDP. Direct connect with client.connect works in the meantime.
• Players get a version mismatch: the game updated and your server did not. Stop it, run the SteamCMD command again and restart.
• Plugins stopped loading after an update: reinstall Oxide or Carbon. The update replaced their files.
• Lag late in the wipe: RAM use climbs as bases grow. Watch memory in Task Manager or htop, and give the server more or reduce the world size next wipe.
• The address changed: most home connections get a new public IP now and then. Send friends the new one.

The easy way

Self hosting Rust is a great way to learn, but the upkeep never stops: a machine running 24/7 for the whole wipe, a home IP shared with everyone who joins, SteamCMD and Oxide reinstalls on the first Thursday of every month, and wiping files by hand on force wipe day.

A hosted server takes all of that off your plate. Pick a plan (8 GB covers a small map with friends, 12 GB a standard 4000 map), pay, and the server is live in about 60 seconds with its own address and nothing to forward. You get a live console for ownerid and any other command, a file manager for server.cfg and plugins, a Reload plugins button, 3 backups for wipe day, and you can split the monthly cost with up to 9 friends. New customers get half off the first month. See Rust server hosting for plans, or follow how to host a Rust server for the full walkthrough.