Illustration for How to Make a Rust Server in 2026

How to Make a Rust Server in 2026

Create a dedicated Rust server in 2026, hosted or on your own PC, explained step by step.

Want to play Rust with your own rules, your own group and your own wipe schedule instead of joining a random public server? A dedicated Rust server gives you full control over settings, admins and mods. This guide walks through both ways to create one and how to configure it properly from day one.

The two ways to create a Rust server

Before anything else, you need to pick between two very different approaches. This choice affects everything that follows, especially for a game as resource-hungry as Rust.

Option 1: host with a provider

You rent a Rust server from a specialised gaming host. It runs 24/7, survives your PC being off, comes with a web panel to manage files, restarts and wipes, and includes DDoS protection β€” which matters because Rust servers are a frequent target. This is the option almost every serious Rust community uses.

Option 2: run the server on your PC

You install RustDedicated via SteamCMD and run it at home. Free on the software side, but Rust is CPU and RAM hungry: your PC must stay on permanently, you expose your home IP, and you manage port forwarding and wipes manually. Only realistic for a quick private test with 1-2 friends.

Which option should you choose?

For anything beyond a two-person test, go with a host. Rust is one of the heaviest games to self-host β€” a decent host plan starts around €12-20/month and removes the DDoS risk, the always-on requirement and the manual wipe hassle entirely. See our full [Rust server cost guide](/en/guides/rust/rust-server-cost) for real prices.

Creating a Rust server on your own PC

If you still want to self-host, here's the procedure using SteamCMD.

1

Install SteamCMD

Download SteamCMD from Valve's site and extract it to a folder, e.g. C:\steamcmd on Windows or ~/steamcmd on Linux. Launch it once (steamcmd.exe or ./steamcmd.sh) to let it self-update.
2

Download the Rust dedicated server files

Inside SteamCMD, log in anonymously and pull the Rust dedicated server files (Steam app ID 258550):
login anonymous force_install_dir ./rustserver app_update 258550 validate quit
3

Launch RustDedicated

In the install folder, run RustDedicated.exe (Windows) or ./RustDedicated (Linux) with your startup parameters, for example:
RustDedicated.exe -batchmode +server.hostname "My Rust server" +server.port 28015 +server.maxplayers 50 +server.worldsize 3000 +server.seed 123456 +rcon.port 28016 +rcon.password "changeme"
4

Open the network ports

For friends to connect from outside your network, set up port forwarding on your router: 28015 UDP for the game itself, plus the query port (usually 28015 or 28016 depending on config) and 28016 TCP if you want remote RCON access. Every router's interface differs, so search "port forwarding [your router model]" if needed.
5

Share your public IP

Your friends connect using your public IP (find it by searching "my ip" on Google) plus the game port, e.g. 86.12.34.56:28015. Warning: most residential connections use a dynamic IP that can change on router restart, breaking the connection until you share the new one.

The limits of a home server

Rust is one of the most demanding games to self-host: it needs a strong single-thread CPU and several GB of dedicated RAM just idling, on top of your own PC use. Your server goes down with your PC, your upload bandwidth caps how many players can connect smoothly, and you're personally exposed to the DDoS attacks that public Rust servers regularly attract. For anything beyond a private test, a host is the safer and often cheaper option.

Configuring your Rust server: the essential settings

Whether hosted or self-hosted, these are the server.cfg commands you'll touch most often.

CommandExample valueWhat it does
server.hostname"My Rust server"Name shown in the server browser
server.maxplayers100Maximum number of simultaneous players
server.worldsize3500Map size in meters (3000 tight PvP, 4000-4500 for 150-250 players)
server.seed123456Map generation seed β€” reuse it to regenerate the same map
server.saveinterval300Auto-save interval in seconds
server.description"Modded, weekly wipe"Description shown in the server browser
rcon.port28016RCON port (TCP) for remote admin access
rcon.password"changeme"Password required to connect via RCON
server.pvefalseEnables PvE mode (disables player vs. player damage)

These are the commands you'll set on day one. Most hosts also expose them as friendly toggles in the panel, so you rarely need to edit server.cfg by hand.

Managing your Rust server: wipes, backups and RCON

Understanding and scheduling wipes

A **wipe** resets the map (and often blueprints) to give everyone a fresh start. Facepunch pushes a **forced wipe** on the first Thursday of every month alongside its update β€” every server must at least map-wipe because the update changes the network protocol, so there's no opting out. Most communities also run their own mid-cycle wipes (weekly or bi-weekly) on top of the forced one. On a host, scheduling a wipe is usually a one-click "reset world" action in the panel that regenerates the map with a new (or fixed) seed.

Backing up your server

Save files live in the server's root folder as `.sav` files, alongside the `server.cfg` and `oxide/` folder if you run plugins. On a host, download these via the file manager or SFTP before a big update. Some hosts offer automatic scheduled backups β€” worth enabling if your community has been running the same map for weeks.

Remote administration via RCON

Once `rcon.port` and `rcon.password` are set, you can connect with a dedicated RCON client (or your panel's built-in console) to run admin commands without being in-game: kicking, banning, broadcasting messages, or checking server performance (`serverinfo`, `fps`) in real time.

Going further with Oxide/uMod plugins

Almost every serious Rust server runs on **Oxide** (distributed via umod.org), the near-universal modding and admin framework for Rust. It adds permissions, kits, teleport commands, better chat, and hundreds of other plugins. Installing it is usually a one-click option in a Rust-focused host's panel; self-hosted, it means dropping the Oxide DLL into your server folder. Expect it to add noticeably to your RAM footprint as you add more plugins.

Useful RCON / F1 admin commands

kick PlayerName β€” kick a player. ban PlayerName β€” ban by Steam ID or name. save β€” force an immediate save. serverinfo β€” show current player count, FPS and entity count.

Ready to launch your Rust server?

Take the 2-minute quiz to get a host matched to your target population, or compare every Rust plan side by side.

Frequently asked questions

How much RAM does a Rust server need?
A small vanilla server (up to ~50 players) runs fine on 8-12 GB. Add Oxide plugins or push past 50-100 players and you should plan for 16-18 GB. Large communities of 150+ players with heavy plugin loads often need 24 GB or more. Map size (server.worldsize) also drives RAM use independently of player count.
How much does hosting a Rust server cost?
Entry-level plans start around €12-20/month for 8-12 GB, enough for a small server. A well-populated mid-size community typically costs €20-30/month, and large 150+ slot servers can reach €40-60/month or more. See our [full Rust server cost guide](/en/guides/rust/rust-server-cost) for real plan-by-plan pricing.
What is a Rust wipe and how often does it happen?
A wipe resets the map (and sometimes blueprints) for a fresh start. Facepunch forces a wipe on the first Thursday of every month with its monthly update β€” this is mandatory for every server. Many communities layer additional wipes (weekly or bi-weekly) on top of that forced one.
What is Oxide/uMod and do I need it?
Oxide is the standard modding and admin framework for Rust, distributed via umod.org. It's not required to run a server, but it's how you add permissions, kits, custom commands and hundreds of quality-of-life plugins. Most Rust-focused hosts let you install it in one click from the panel.
How many players can a Rust server support?
There's no hard engine cap β€” public servers commonly run 100 to 300 slots. What limits you in practice is server hardware: RAM, CPU clock speed and map size all need to scale up together as you raise server.maxplayers.
Which ports does a Rust server use?
The game port defaults to 28015 (UDP) and is what players connect to. RCON, for remote admin access, defaults to 28016 (TCP). If you self-host, both need to be forwarded on your router; on a host, this is handled automatically.
Can I change the map size and seed after launch?
Yes, but changing server.worldsize or server.seed regenerates the map from scratch, which erases the current world β€” effectively a wipe. Plan seed and size changes for a scheduled wipe rather than mid-cycle.
Is my Rust server online if I'm not connected?
Yes, if you use a host β€” the server runs 24/7 independently of your own connection. If you self-host, the server goes down the moment your PC shuts down, restarts or loses power.
Our recommendation

Ready to launch your Rust server?

Here are the best Rust hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.

My box 12

Minestrator

17.99€/month
-10% with code HOSTMYGAME
Max players:50
Mods:
Yes

Specifications

RAM:12GB(DDR4)

Compatible games

Rust

Features

  • βœ“DDoS Protection
  • βœ“Backups

Wood

Shockbyte

12.84€/month
-25% with code LAUNCH
Max players:40
Mods:
Yes

Specifications

RAM:8GB(DDR4)

Compatible games

Rust

Features

  • βœ“DDoS Protection
  • βœ“Oxide mod support
  • βœ“Instant Setup
  • βœ“24/7 Support

Rust Starter

Hosterfy

19.99€/month
Max players:Unlimited
Mods:
Yes

Specifications

RAM:12GB(DDR4)

Compatible games

Rust

Features

  • βœ“DDoS Protection
  • βœ“100% FranΓ§ais
  • βœ“Slot illimitΓ©