Dedicated Rust server for hardcore survival, base building, and raiding with admin control
Grab the automated bash script from GitHub to follow along with the video.
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/gaming/rust/rust-ubuntu.sh
chmod +x rust-ubuntu.sh
sudo bash rust-ubuntu.shThe script installs Docker, pulls the Rust dedicated server image, and downloads game server files. The initial download is ~8 GB. The server runs on port 28015 UDP for game traffic and 28016 TCP for RCON.
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/gaming/rust/rust-ubuntu.sh
chmod +x rust-ubuntu.sh
sudo bash rust-ubuntu.shSet environment variables for server name, map seed, max players, and RCON password. These are configured in the Docker environment or .env file created by the installer.
# Edit the server environment file
nano /opt/rust/.env
# Key environment variables:
# RUST_SERVER_NAME="My Rust Server"
# RUST_SERVER_SEED=12345
# RUST_SERVER_WORLDSIZE=3000
# RUST_SERVER_MAXPLAYERS=50
# RUST_RCON_PASSWORD=yourrconpass
# RUST_OXIDE=trueOpen Rust, go to Play, then Community to search for your server name, or use the F1 console to connect directly with the client.connect command.
# In-game F1 console direct connect
client.connect <your-server-ip>:28015Manage your server remotely via RCON. Connect using a web RCON client or rcon-cli tool. Common admin tasks include kicking/banning players, saving the world, and reloading plugins.
# Connect via RCON CLI
docker exec -it rust-server rcon-cli --port 28016 --password yourrconpass
# Common RCON commands:
# players - list connected players
# kick STEAMID - kick a player
# ban STEAMID - ban a player
# server.save - save the world
# oxide.reload * - reload all plugins
# View live logs
docker logs -f rust-server| Port | Purpose |
|---|---|
| 28015 UDP | Game traffic (player connections) |
| 28016 TCP | RCON remote administration |
Rust is a multiplayer survival game focused on intense PvP, base building, and resource gathering. A dedicated server allows you to host your own Rust community with custom world seeds, population sizes, wipe schedules, and Oxide plugins for enhanced gameplay.
Running your own Rust server lets you control the wipe schedule, map size, server population, and install Oxide/uMod plugins for custom game modes. You can run a low-population friends server or a full community server with hundreds of players.
Rust uses UDP port 28015 for game connections and TCP port 28016 for RCON. Open UDP 28015 for players. Keep TCP 28016 (RCON) firewalled and accessible only from trusted IPs. The Steam query uses port 28017 UDP for server browser listing.
Alternatives include renting from server hosting providers (GTXGaming, Nitrado), official server clusters, and community server platforms. Self-hosting gives maximum control but requires weekly maintenance during Rust's Thursday updates.
Avoid self-hosting Rust if you cannot maintain the server through weekly Thursday patches — an outdated server empties quickly. Also avoid on low-CPU hardware; Rust is one of the most CPU-demanding game servers available.
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support. Whether you need a single-server setup or a multi-site network, our team ensures your infrastructure is built right, secured properly, and maintained reliably.
Rust releases mandatory updates every Thursday (Devblog Thursday). After each update, clients are on the new version and cannot connect to old server versions. You must update your server within hours of each patch. Automate this with a script that checks for updates and restarts the server after updating.
Oxide (now uMod) is a modding framework for Rust that allows server plugins written in C#. It enables features like admin GUI panels, economy systems, teleportation commands, shop systems, clan management, vote kick, and hundreds of other custom gameplay elements. Most community servers install Oxide for essential admin tools.
A wipe deletes the map and returns all resources to the default state — all bases and items are gone and everyone starts from scratch. Map wipes are usually done monthly or bi-weekly to keep gameplay fresh. Blueprint wipes (wiping research progress) are less frequent. Most servers announce wipe schedules in advance.
Rust servers typically support 50 to 200 players. Performance scales primarily with CPU single-thread speed, not core count — Rust is heavily single-threaded for game logic. A high-clock CPU (3.5+ GHz) can handle 100 players. Large community servers with 200+ players need very powerful dedicated hardware.
Minimum: 4 CPU cores at 3.5 GHz, 8 GB RAM, 15 GB disk. For 50 to 100 players: 8 cores at 4+ GHz, 16 GB RAM, and 30 GB fast SSD. Rust is unusually demanding — a slow CPU will cause server-side lag (high frame time) even with few players connected.
Set a specific -seed value in the server startup command to reproduce a known map layout, or set it to 0 for a random seed. Control map size with -worldsize (e.g., 3500 for a standard map). Custom procedural maps are defined by seed + size combination. Custom hand-crafted maps can be loaded via the -levelurl flag.
Via RCON or server console: banid STEAMID64 reason. This adds the player to the serverauto.cfg banlist. To ban via in-game admin: press F1, type ban STEAMID64. You can also add Steam IDs to the ban.cfg file manually. Use oxide plugins for more advanced moderation with UI-based ban management.
Yes — Rust has a native Linux dedicated server binary available via SteamCMD. Linux servers typically have better performance per cost compared to Windows VPS. Docker images based on Ubuntu with SteamCMD make deployment and updating straightforward.