How to Host a Rust Server in 2025: Setup & Optimization Guide

Rust is one of the most demanding survival games to host. Between large map sizes, physics calculations, AI scientists, and player-built bases loading thousands of entities, your server hardware gets pushed hard. This guide walks you through everything you need to know about Rust server hosting — from choosing the right hardware to configuring your server, installing plugins, and keeping performance stable through wipe cycles.

Rust Server Hardware Requirements

Rust's dedicated server (RustDedicated) is heavily single-threaded for its main game loop. That means raw clock speed matters far more than core count. Here's what you need for a smooth experience:

• CPU: 4+ GHz single-core boost. AMD Ryzen 9 9950X or Intel i9-14900K are ideal. Rust's tick loop runs on one thread, so IPC and clock speed are king.
• RAM: 8 GB minimum for a small vanilla server. 12-16 GB recommended for modded servers with 100+ players and large maps (4000+ size). Rust leaks memory over long sessions, so headroom matters.
• Storage: NVMe SSD required. Map saves, player data, and oxide plugin data all hit the disk regularly. A Gen4 NVMe with at least 50 GB free is recommended.
• Network: 1 Gbps minimum with low latency. Rust sends frequent position updates for all entities. A server with 200 players on a 4500-size map can easily push 50+ Mbps of sustained traffic.

Managed Hosting vs. VPS: Which Should You Choose?

You have two main paths when deciding how to host a Rust server: managed game hosting panels or a self-managed VPS/dedicated server.

Managed game hosting gives you a web panel (like Pterodactyl or TCAdmin) with one-click installs, automatic updates, and preconfigured settings. It's great for beginners, but you're often limited in what you can customize and share hardware with other customers.

VPS or dedicated server hosting gives you full root access, letting you tune kernel parameters, manage your own firewall, and allocate resources exactly how you want. This is the better option for serious communities running modded servers with custom plugins. At GoodLeaf, our game servers run on dedicated AMD Ryzen hardware with NVMe Gen5 storage, giving you the single-threaded performance Rust demands without sharing resources.

Installing RustDedicated via SteamCMD

SteamCMD is the command-line tool Valve provides for downloading and updating dedicated server files. Here's how to install Rust's dedicated server on Linux:

# Install SteamCMD (Ubuntu/Debian)
sudo apt update && sudo apt install steamcmd -y

# Create a directory for your server
mkdir -p ~/rustserver && cd ~/rustserver

# Download RustDedicated (App ID 258550)
steamcmd +force_install_dir ~/rustserver \
  +login anonymous \
  +app_update 258550 validate \
  +quit

After installation, you'll have the RustDedicated binary ready to launch. To update the server before each wipe, simply re-run the app_update 258550 command through SteamCMD.

Server Configuration: server.cfg, Map Size, Seed & Tick Rate

Rust server configuration is handled through startup parameters and the server.cfg file located in your server's cfg directory. Here are the key settings:

• server.worldsize — Map size in meters. Default is 4500. Smaller maps (3000-3500) suit 50-100 players; larger maps (4500-6000) suit 200+ players.
• server.seed — The procedural generation seed. Each seed produces a unique map. Use rustmaps.com to preview seeds before committing.
• server.tickrate — How many times per second the server processes the game loop. Default is 30. Keep it at 30 unless you have extremely powerful hardware; going higher increases CPU load dramatically.
• server.maxplayers — Maximum concurrent players. Set this based on your hardware and map size. A common ratio is roughly 1 player per 20-25 square meters of map.
• server.hostname — Your server's display name in the server browser. Include key details like wipe schedule and group size.
• decay.scale — Controls how fast buildings decay. Default is 1.0. Modded servers often set this lower to reduce upkeep burden.

# Example launch command
./RustDedicated -batchmode \
  +server.port 28015 \
  +server.hostname "My Rust Server | 2x | Wiped 02/05" \
  +server.worldsize 4000 \
  +server.seed 123456 \
  +server.maxplayers 150 \
  +rcon.port 28016 \
  +rcon.password "YourSecureRCONPass" \
  +rcon.web 1

Essential Plugins: Oxide/uMod

Oxide (also known as uMod) is the de facto modding framework for Rust. It injects a plugin loader into the server, allowing community-made C# plugins to extend functionality. Install it by downloading the latest Oxide build and extracting it into your server's root directory.

Here are the most popular plugins every modded Rust server should consider:

• Gather Manager — Adjusts resource gathering rates. Essential for 2x, 3x, or 5x servers.
• Kits — Gives players starter kits or VIP kits on a cooldown timer.
• NTeleportation — Adds /home, /tpr (teleport request), and /town commands.
• Quick Smelt — Speeds up furnace smelting for modded servers.
• Clans — Adds clan tags, friendly fire protection, and clan chat.
• BetterChat — Customizes chat formatting with colors, titles, and group prefixes.
• Stack Size Controller — Lets you increase item stack sizes beyond vanilla limits.

RCON and Server Administration

RCON (Remote Console) lets you manage your Rust server without SSH access. With rcon.web 1 enabled, you can connect via any WebRCON client in your browser. Popular tools include RustAdmin and rcon.io.

Common RCON commands every admin should know:

• status — Lists all connected players with SteamIDs
• kick/ban [steamid] "reason" — Removes or permanently bans a player
• say [message] — Broadcasts a server-wide message
• server.save — Forces an immediate world save
• server.writecfg — Writes current config values to server.cfg
• oxide.reload [plugin] — Hot-reloads a specific plugin without restart

Wipe Schedules and Map Management

Facepunch enforces a forced wipe on the first Thursday of every month with each major update. Beyond that, server owners choose their own wipe cadence. Common schedules include:

• Weekly wipes — Popular for high-pop PvP and competitive servers. Keeps the gameplay fresh but requires more admin work.
• Biweekly wipes — A balance between fresh starts and player progression. Common for modded 2x-3x servers.
• Monthly wipes — Forced wipe only. Best for vanilla or lightly modded servers where players want long-term base building.

During a wipe, you delete the map save file and optionally the player blueprint data. Map wipes reset buildings and loot while keeping learned blueprints. Full (BP) wipes reset everything including blueprints, leveling the playing field completely. Keep backups of your save files before every wipe in case you need to roll back.

DDoS Protection for Rust Servers

Rust servers are frequent DDoS targets, especially competitive and high-population servers. Attacks typically hit the game port (28015) with UDP floods designed to overwhelm the connection or cause packet loss that makes the server unplayable.

Generic web-based DDoS protection like Cloudflare does not work for game servers because Rust uses raw UDP, not HTTP. You need a host with network-level game traffic filtering that can distinguish legitimate Rust packets from attack traffic. GoodLeaf uses Path.net's 17 Tbps backbone with custom game filters, scrubbing malicious traffic at the edge before it ever reaches your server.

Performance Optimization Tips

Once your server is live, these optimizations help maintain a stable tick rate as the wipe progresses and entity count grows:

1. Limit entity count: Use plugins like Entity Cleanup or adjust decay rates so abandoned bases don't pile up. Entity count is the single biggest factor in server performance.
2. Set a reasonable map size: Don't run a 6000-size map for 50 players. More map means more entities, more AI patrols, and more memory usage.
3. Schedule restarts: Restart the server every 12-24 hours during off-peak times. Rust's server process accumulates memory over time, and a restart clears it.
4. Optimize your save interval: The default save interval is 600 seconds. On servers with massive entity counts, saves cause brief lag spikes. Scheduling saves during low-activity hours helps.
5. Monitor tick rate: Use the perf command in RCON to check tick rate in real time. Healthy servers maintain 28-30 ticks consistently. If it drops below 20, investigate entity count and plugin performance.
6. Use a RAM disk for saves: On Linux, mounting your save directory as a tmpfs RAM disk eliminates disk I/O lag during saves. Sync to persistent storage on a schedule.

Frequently Asked Questions