Rust Server Hosting
Run your Rust server on a VDS of your own: you choose the map size, the wipe schedule and the plugin framework. Your server runs in Istanbul, protected at no extra cost by TRSHIELD's Rust profile.
Extreme packages for Rust
Rust's memory needs grow with map size and player count, so check the memory figure on each card when you choose. In every package, the vCores are dedicated to you.
TR-9950X-8GB
TR-9950X-12GB
TR-9950X-16GB
TR-9950X-20GB
TR-9950X-24GB
TR-9950X-32GB
TR-9950X-48GB
TR-9950X-64GB
Rust server requirements
You download the Rust dedicated server files directly to your VDS with SteamCMD using an anonymous login and pull updates with the same tool. The server runs on both Windows Server and Linux.
The Rust server process itself requires at least 12 GB of free RAM and 15 GB of disk space, and memory usage climbs further on large 6k procedural maps or busy servers. Fast NVMe storage is essential to keep world saves and entity loading smooth.
As player count and base building scale up, single-core CPU clock speed is what keeps server tick rate steady. Our Extreme VDS packages combine an AMD Ryzen 9 9950X overclocked (OC) to 5.9 GHz, DDR5 6400 MHz memory and Samsung 990 Pro Gen4 NVMe SSDs for demanding wipe days.
Which package should you start with?
On top of the 12 GB of free RAM required by the Rust server process itself, the operating system and your Oxide or Carbon framework add their own overhead. Starting with an Extreme package that provides 16 GB or more of DDR5 RAM gives your server comfortable headroom.
- Small community
- For a group of friends or a newly launched server, pair a 16 GB RAM Extreme package with a small or medium map.
- Growing server
- CPU load rises as your player count and plugin list grow. The next package up adds vCores, memory and NVMe together.
- Large map, long plugin list
- For a 6k map or a server running many plugins, look at the upper packages.
- Your busiest hour
- Plan capacity for your busiest hour, not a quiet one, and check CPU and memory use while the server is full.
The wipe schedule is yours to set
A wipe starts a Rust server over with a fresh cycle. A map wipe deletes the map and everything players have built on it; a blueprint wipe also resets the blueprints players have learned. Facepunch's forced wipes only reset the map, so wiping blueprints is up to you.
Players search the server browser by weekly, biweekly and monthly wipe tags, and you set your server's tag. By default, Rust's wipe timer follows Facepunch's forced wipes, which fall on the first Thursday of the month; you can change its day, hour and time zone in your server settings. The in-game countdown and the events on the final day before a wipe follow that setting.
You can put the wipe and the update before it into a script and let the operating system's scheduler run it at your community's hour.
Modded servers with Oxide or Carbon
To run plugins on a Rust server, you first install a modding framework. Oxide, distributed through uMod, offers thousands of community plugins, while Carbon provides a modern alternative designed for compatibility with Oxide plugins.
Because the two frameworks do not run side by side in the same install, you pick the one that best fits your setup. You can structure your startup script so that after each Rust update, SteamCMD updates the base game files first and applies your modding framework right after.
If you want a different ruleset without plugins, you can enable built-in game modes such as softcore or primitive in your server settings at the start of a new wipe cycle.
Game, query, RCON and Rust+ in one profile
A Rust server opens four doors to the outside: the game port players connect to, the query port the server browser reads from, RCON for remote administration, and the port the Rust+ app connects to. For your server to appear in the server browser, the query port has to be publicly reachable. Even on private or whitelisted servers, an IP address can eventually become public, making strong DDoS protection essential for smooth gameplay.
TRSHIELD's Rust profile handles all four in a single template: queries from the server browser are answered from cache, and RCON's web connection and Rust+ traffic are filtered by the same profile. The Rust profile is free on every package, and the 12 Tbps TRSHIELD network behind it defends against every known attack vector and is continuously developed.
Istanbul, if your players are in Turkey
Raids and gunfights in Rust call for split-second reactions. As latency between player and server rises, shots and movement reach the server later, and players feel it as stutter and delayed response. The same delay hits closing a door or repairing a wall during a raid.
When most of your players are in Turkey, opening the server in Istanbul shortens the route between them and the server. Our Extreme servers are hosted at Mars Istanbul Data Center, which is carrier-neutral. Rust detects your server's country from its IP address and displays it in the server browser; with our Istanbul IP addresses, your server appears directly under Turkey in the list.
Before you choose a package, measure your connection's latency to our servers with the Ping Test. Before you announce the server, ask a few of your players to run the same test too, especially those connecting from abroad.
What you decide on your own VDS
Test branch
Before taking a major update to your live server, you can try Facepunch's staging branch on a separate test server.
Custom maps
You choose the seed and size of the procedural map, or run a custom map. Because players download custom map files from a URL you provide, you can host the map file directly on a lightweight web server on the same VDS rather than relying on public file-sharing sites.
Rust+ and RCON
Manage your server remotely over WebRCON and open the Rust+ companion port so your players can follow smart alarms and team chat from their phones.
More than one server
Give each server its own server.identity name and its own ports, and you can run several Rust servers from the same install; CPU and memory needs grow with the number of servers.