How to host a Rust server (2026)

Short answer. You can host a Rust server yourself for free: install the Rust Dedicated Server (Steam app 258550) with SteamCMD and an anonymous login, start RustDedicated with a RCON password and a world size, and open UDP 28015 (game) plus the query port. Or rent a Rust server and skip the networking.

Players join by finding your server in the in-game server browser or by pressing F1 and typing the connect command with your address and port.

Checked on 5 November 2026, when the newest monthly update in Rust's Steam announcements was Livestock (1 October 2026). Facepunch's monthly updates have landed on the first Thursday of each month all through 2026, and the server's default wipe timer counts down to the first Thursday at 19:00 London time, so plan to update your server on that day.

This guide uses Facepunch's own server documentation and what we run on every Rust server we host. To go straight to the rental route, see Option 2.

What you need

• The server software: "Rust Dedicated Server", Steam app 258550. It downloads with an anonymous login. You do not need a Steam account to run a server, but every player needs Rust on Steam.
• A machine that stays on: Windows, Linux or macOS. Facepunch's server documentation lists the memory it needs (a 6000 size map uses more) and asks for at least 15 GB of free disk space, with SSD or NVMe strongly preferred. This guide uses Linux, which is what we run.
• Network: the game port (default 28015, UDP) and the query port (UDP) reachable from the internet. RCON uses a TCP port, and the Rust+ companion app uses its own TCP port.
• A RCON password: choose your own. Facepunch's example sets one on the command line, and outside admin tools connect with it.
• Your SteamID64: the 17-digit number of your Steam account, to make yourself admin.

Option 1: host it yourself

These steps are for a Linux machine. The SteamCMD commands are the ones Facepunch publishes.

Install the server

1. Install the library SteamCMD needs on Debian or Ubuntu.

   sudo apt-get install lib32gcc-s1

2. Install SteamCMD.

   mkdir steamcmd
   cd steamcmd
   wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz
   tar xvfz steamcmd_linux.tar.gz
   chmod +x steamcmd.sh

3. Let SteamCMD update itself once. A fresh SteamCMD updates itself and restarts on its first run. Our install script runs ./steamcmd.sh +quit first for that reason: a download issued across that restart can fail with "Missing configuration".
4. Download the server.

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

   Leave out +login and Steam answers "Failed to install app '258550' (No subscription)". Our install script also checks that steamapps/appmanifest_258550.acf exists afterwards and runs the download again if it does not, because SteamCMD has reported success on our installs and left no game files. Do the same with ../rust/steamapps/appmanifest_258550.acf.

Start it

1. Run the server from the rust folder. This is the shape of the command line we use, with the options you will change:

   ./RustDedicated -batchmode +server.port 28015 +server.identity "server1" +server.hostname "My Rust server" +server.maxplayers 50 +server.level "Procedural Map" +server.worldsize 3000 +server.seed 12345 +rcon.port 28016 +rcon.web true +rcon.password "choose-a-long-password"

   Facepunch allows a world size from 1000 to 6000 and a seed from 0 to 2147483647. Larger maps need more disk and memory. server.identity is the name of the folder that holds this server's files. To keep the server running with its output visible, Facepunch suggests running it inside screen.
2. Wait for the ready line. Facepunch says the server takes several minutes to start fully. It is ready when the console prints Server startup complete.

Open the ports

• Game: UDP 28015, or whatever you set with +server.port. Allow it on the firewall (for example sudo ufw allow 28015/udp) and forward it on your router.
• Query: UDP, and it must differ from the game port. Facepunch says the server browser needs it. If you do not set +server.queryport, Rust uses one more than the larger of the game port and the RCON port: 28017 with the command above, so open it too (sudo ufw allow 28017/udp).
• RCON and Rust+: TCP, only if you use an outside RCON tool or the Rust+ companion app. Facepunch says only the game port is needed to connect and play. Do not expose RCON with a weak password.
• Give the machine a fixed local address, so your router rule keeps pointing at it.

Become admin and join

1. Make yourself admin. With the server stopped, add a line to server/server1/cfg/users.cfg (use your own identity in the path):

   ownerid 76561198000000000 "YourName" ""

   Start the server again and join to get the owner level. With the server running you can instead type ownerid with your SteamID64 in the server console or over RCON, then reconnect. Facepunch also documents moderatorid for a moderator.
2. Join it. In Rust press F1 and type connect your.ip.address:28015. On the same machine, connect localhost:28015 works.
3. Update every month. Stop the server and run the download command again on the first Thursday of the month, when Facepunch releases its monthly update.

Oxide and Carbon plugins

Facepunch notes that Oxide must be reinstalled after each server update (Oxide releases a new version shortly after), and that running SteamCMD in your start script puts the files back to vanilla. If you use Carbon instead, follow Carbon's own update instructions after each Rust update.

Option 2: host it on PlayNHost

Renting removes the install, the ports, the firewall and the monthly update routine. You still choose a name, a map and your rules.

1. Pick a plan. Open the Rust server hosting page and compare the plans: WORKBENCH LEVEL 1 (40 players), WORKBENCH LEVEL 2 (70) and WORKBENCH LEVEL 3 (125) at the time of writing. Press Create Server (Customize Plan on WORKBENCH LEVEL 3) and finish the order. Prices change, so check them on that page.
2. Wait for the install. The server appears in the panel. Its Console prints Server startup complete when it is ready.
3. Name it and pick the map. On the Settings page set the Server Name, World Size and World Seed (a number from 1 to 2147483647), then restart. A seed change takes effect at the next start, but the old map stays on disk until you wipe, so change the seed as part of a map wipe. See How to choose your Rust world size and seed.
4. Choose plugins or vanilla. Pick vanilla, Oxide or Carbon under Modding Framework. See How to switch your Rust server between Oxide and Carbon.
5. Invite your players. The Play with friends card on Overview shows how they join, and Copy invite message copies it. See How to join your Rust server.

What the panel does for you:

• An RCON password is generated for your server and shown under Settings. You only need it for outside tools such as RustAdmin. The panel's own console works without it. If you clear it or want to change it, see Your Rust server will not start without an RCON password.
• Ports are assigned and open from the start. The game, query, RCON and Rust+ ports are filled in on the startup line for you.
• With Auto Update on (the default, under Show advanced on the Settings page), the server checks Steam for a new build every time it starts, which matters on the first Thursday of the month. See How to update your Rust server.
• The plugin framework installs itself again at every start, so a game update never strips Oxide or Carbon.
• Leaving Oxide is a setting too: switch to Carbon or vanilla and the server restores Rust's original game files at the next start, so no Oxide file is left behind.
• Moving between the Release and Staging branches is the Branch setting, not a SteamCMD session. See How to switch your Rust server to the staging branch.
• Wipes have their own Wipe page with a Back up first option that takes a backup before anything is deleted. See How to wipe your Rust server.

Self-hosting or renting: an honest comparison

• Cost: the server software is free. Self-hosting costs hardware, power and bandwidth, or a cloud machine, with the memory Facepunch's documentation lists. Renting is a monthly fee set by the plan.
• Uptime: a home server is only up while your PC, power and internet are. A rented server runs on the host's hardware.
• Exposure: at home, players connect to your public IP address and you look after the firewall and router. A rented server keeps your home IP out of it.
• Monthly update: self-hosting means stopping the server, running SteamCMD and updating your plugin framework each time. On our servers Auto Update and the framework reinstall happen at start.
• Control: self-hosting gives you every file and every startup option. On our servers you still have the Files tab, Additional Arguments and RCON for your own tools.

Ready to skip the setup? See the Rust server plans. Already have a server? Start with How to set up your Rust server: key settings.