Guide Rust

Rust Dedicated Server Setup with SteamCMD

Create a Rust PC dedicated server on Windows, Linux or macOS using SteamCMD 258550. Configure UDP game/query ports, server.cfg, RCON and backups.

rust game artwork
Source: coop-legends.de

Overview

You can self-host a Rust dedicated server on Windows, Linux or macOS. Facepunch distributes server files through SteamCMD and does not require a personal Steam account to install the server. This guide follows the official Rust Wiki as reviewed on September 3, 2026.

Managed hosting is another option for operators who do not want to maintain hardware, software and network access. Rust Console Edition is a separate ecosystem; these instructions cover PC Rust servers only.

Rust dedicated-server requirements

Facepunch recommends a rough starting baseline of 12 GB of free RAM and 15 GB of available storage, preferably SSD or NVMe. Actual requirements depend on map size, server population and configuration, and larger maps can need substantially more memory.

An internet-facing self-hosted server requires reachable network ports in your firewall and, behind a router, suitable forwarding. Cloud or VPS setups may also require firewall changes in the provider's control panel.

Install Rust with SteamCMD

  1. Install SteamCMD for your server operating system.
  2. Choose a dedicated directory.
  3. Use the Rust dedicated-server App ID 258550.
  4. Choose login anonymous for an account-free download.

Facepunch provides the following Linux example:

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

Rerun the same app_update operation to update the files, after stopping the running server.

Launch and configure the server

Facepunch recommends limiting the launch command to essential parameters and putting longer-term settings in server.cfg. A minimal Windows example with custom values is:

RustDedicated.exe -batchmode +server.port 28015 +server.queryport 28016 +server.level "Procedural Map" +server.seed 1234 +server.worldsize 3000 +server.maxplayers 10 +server.hostname "My Rust Server" +server.identity "coopserver" -logfile rustserverlog.txt

Default game traffic uses UDP 28015. The query port must also be externally reachable over UDP and must be different from the game port. Optional RCON uses a distinct TCP port and must be secured with a strong password.

Use server.cfg for persistent settings

Facepunch stores per-instance configuration under:

server/<server.identity>/cfg/server.cfg

For example:

server.maxplayers 10 server.hostname "My Rust Server"

Unlike launch arguments, settings within server.cfg are written without an initial plus sign. Prefer controlled shutdown before editing and restart afterward.

Game, query and RCON ports

The configured server.port and server.queryport must be reachable over UDP. Without a separately set query port, Facepunch documents a default of one greater than the higher value of server.port or rcon.port. The game and query ports may not be identical.

RCON and Rust+ use TCP. Query reachability is needed for the public server browser. Do not open unused RCON or Rust+ ports merely as a precaution.

For a same-PC test, open Rust's F1 console and use connect localhost:28015. External friends need the server's externally reachable address rather than localhost.

Admin privileges and backups

Run users in the server console to identify connected players and their Steam IDs. To designate an owner, Facepunch documents a command such as ownerid STEAMID "Name"; the player must reconnect for permissions to take effect.

World files, player data and configuration live in the directory assigned by server.identity. Stop the server cleanly and back up that entire identity directory to preserve the world and settings.

Rent or self-host a Rust server?

Self-hosting provides full control over saves, patches and plugins but requires ongoing maintenance, firewall setup and backup routines. Managed servers charge a recurring fee while handling some operational tasks. Compare slots, real CPU/RAM allocation, storage, mod/plugin support, backup export, server region and complete server.cfg access—not simply the cheapest initial price.

The game port defaults to UDP 28015. A public server also needs a separate reachable UDP query port. RCON and Rust+ use their own TCP ports.

No. SteamCMD can download the server with anonymous login. Playing Rust itself still requires an appropriate player account and game entitlement.

Under server//cfg/server.cfg, where server.identity is set when launching the server.

Technically yes, but a separate machine generally suits permanent hosting better because the client and server compete for CPU and RAM.

See our Rust game profile for multiplayer modes and platforms.

Sources