Rust Server HostingRust Server Hosting
RustDedicated on Ryzen 9 9950X in İstanbul, with Oxide or Carbon plugins, WebRCON access and full control over how and when you wipe.
Choose your Game Server
Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.
1. Plan Type
2. Location
3. Choose Plan
Gold 8GB
Platinum 10GB
Diamond 12GB
Emerald 16GB
Xtreme 32GB
Which Rust Plan Is Right for You?
Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Gold 8GB | 3000 map, 20–30 players, light pluginsRight for a friend group or small clan; keep an eye on memory in the last week of a wipe. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | 3000–3500 map, 30–50 playersA balanced tier for community servers running gather, kit and teleport plugins. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | 3500–4000 map, 50–80 playersAbsorbs late-wipe entity buildup comfortably and leaves room as your plugin list grows. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | 4500 map, 80–150 players, moddedSix vCores and 16 GB: our recommended tier for busy modded servers and custom maps. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | Large/custom map, 150+ players, heavy pluginsBuilt for big communities, event servers and plugin-heavy setups from wipe day to the last hour. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
Why TheCrewHost for Rust?
On a Rust server the real load comes from entities and plugins piling up over a wipe, so that is what we planned the hardware around.
Oxide/uMod and Carbon plugins
Drop .cs plugin files into oxide/plugins or carbon/plugins and the framework compiles them on the fly, generating JSON configs you can edit and hot-reload without a restart.
Full WebRCON control
With rcon.web enabled, connect any WebRCON client to check who is online, kick or ban, broadcast with say and force a server.save without launching the game.
Map wipes vs. blueprint wipes
Delete the .map and .sav files for a fresh island, and decide separately whether the player.blueprints databases go too. Map-only or full BP wipe is your call.
Zen 5 single-thread speed
Most of the Rust simulation runs on the main thread, so high clock speed matters more than core count. The 9950X keeps server FPS up when the server is packed.
NVMe for growing save files
The .sav file grows every day of a wipe and is rewritten on each save interval. Samsung 990 EVO Plus NVMe keeps that write short so the stutter stays brief.
DDoS filtering for wipe night
Attacks tend to land when a server is busiest, which on Rust means wipe night. Free DDoS protection filters the junk traffic so real players stay connected.
TheCrewHost Rust server hosting starts at $11.00 (₺440.00) per month and gets you a RustDedicated install on a Ryzen 9 9950X with DDR5 memory and NVMe storage, sized anywhere from 8 GB to 32 GB. The machine sits in İstanbul, so players in Türkiye and the surrounding region reach it over a short route, which is exactly where it counts: door camps, roof peeks and online raids. You pick the modding framework (Oxide/uMod or Carbon), set world size, seed and player cap through startup parameters, and administer everything over RCON. Whether you follow the first-Thursday forced wipe or run weekly wipes, you have full file access to do it your way.
What can you run on a Rust server?
Your Rust server runs Facepunch's official RustDedicated build, and what you put on top of it is up to you. A plain vanilla server with no gameplay-changing plugins can be listed under the Community tab. Once you add plugins that alter gather rates, hand out kits, add shops or teleports, Facepunch's server guidelines expect you to list under Modded instead, so decide early which audience you are building for.
Popular setups include 2x, 3x and 5x solo/duo/trio servers with team limits, PvE servers running server.pve true, fast-paced battlefield or arena servers with instant crafting, and locked-down private servers for a single clan. Some of that is handled by convars, the rest by plugins.
If you want a custom map built in an editor such as RustEdit, you upload the .map file to a direct-download URL and pass it to the server with the server.levelurl startup parameter. Players download the map from that link on first connect, so host it somewhere that will stay online for the whole wipe.
How much RAM does a Rust server need?
Three things drive Rust memory usage: world size (server.worldsize), concurrent players, and the number of entities players build during the wipe. A fresh 3000 map with a handful of plugins starts out modest, but every wall, door, box, turret and furnace adds entities, and memory usage climbs noticeably toward the end of a monthly wipe.
As a starting point: Gold 8GB covers a 3000 map with 20 to 30 players, Diamond 12GB suits a 3500 to 4000 map with 50 to 80 players, and Emerald 16GB is where a 4500 map with plugins and 100+ players belongs. If you are running a large custom map, dozens of plugins and 150 or more players, Xtreme 32GB leaves real headroom.
On the CPU side, single-thread performance matters more than raw core count, because the simulation leans heavily on the main thread. Storage matters too: the .sav file can reach hundreds of megabytes late in a wipe, and fast NVMe keeps periodic saves from turning into noticeable freezes. When you outgrow a plan, upgrade in place.
How do you install Oxide/uMod or Carbon plugins?
With Oxide installed, you upload a plugin's .cs file to oxide/plugins. Oxide compiles it, creates its config in oxide/config, stores any persistent data in oxide/data and writes language strings to oxide/lang. After editing a config, run oxide.reload PluginName and the change applies without restarting the server.
Permissions are group-based. Create a group with oxide.group add vip, give it a permission with oxide.grant group vip plugin.permission, then put a player in it with oxide.usergroup add PlayerName vip. User and group assignments live in data files under oxide/data, so as long as you do not delete those during a wipe, your VIPs and staff keep their roles.
Carbon is a newer framework that runs the vast majority of Oxide plugins unchanged; its plugins go in carbon/plugins. Because both hook the same game assemblies, you cannot run them together, so pick one. Either way, after each Facepunch update the framework needs its matching new build, or plugins simply will not load until you update it.
How do you manage server.cfg, startup parameters and RCON?
Rust settings live in two layers. Startup parameters are read once at boot and define how the world is generated and who the server is: +server.worldsize, +server.seed, +server.maxplayers, +server.hostname, +server.identity and +rcon.password are the usual suspects. Everything that applies after boot goes into server/your-identity/cfg/server.cfg as one convar per line, which is where values like decay.scale, server.pve and server.globalchat belong.
To make yourself an admin, run ownerid followed by your SteamID64 in the console, then server.writecfg to persist it; that command writes to users.cfg in the same folder. Use moderatorid for moderators.
For remote administration, set rcon.port, choose a long rcon.password and keep rcon.web enabled. Any WebRCON tool can then send status, kick, ban, say and server.save. Treat the RCON password like a root password and share it with as few people as possible. The panel console and file manager cover the same tasks from a browser, while SFTP is the easier route for uploading large maps or plugin bundles.
When is the Rust forced wipe, and how do you run your own schedule?
Facepunch ships its monthly update on the first Thursday of every month, and that update forces a map wipe on every server. When it drops, you update the server files, install the matching Oxide or Carbon build and boot on a new map. Blueprint wipes are not forced every month; whether players keep their unlocks is your decision.
Mechanically, a map wipe means deleting the .map and .sav files in your identity folder. A full wipe also removes the database files starting with player.blueprints. Changing the seed gives players a new island; keeping the same seed and size regenerates the identical map.
Many communities add weekly or biweekly wipes between forced wipes. Frequent wipes pull in fresh players on wipe day and keep entity counts from spiraling. Take a backup from the panel right before wiping so you can roll back if a plugin misbehaves on the new map. If you want wipes driven by a file list instead of manual deletions, look at our Rust Autowipe hosting page as well.
Why does a Rust server lag late in a wipe, and how do you fix it?
Most late-wipe stutter comes from accumulated entities rather than a lack of raw power. Keep decay at a level that actually removes abandoned bases, cap runaway building with a plugin if your ruleset allows it, and schedule a daily restart during your quietest hour so memory is released cleanly.
Plugins are the other big variable. If unloading one plugin makes the hitching disappear, you have found your culprit; do not keep unused plugins sitting in the folder. An overly aggressive save interval also keeps the disk busy for no real gain.
If players see a protocol mismatch after the monthly patch, the server is still on the old build; restart it so the update completes. A brand-new server can take a while to appear in the in-game browser, and in the meantime players can join by pressing F1 and typing client.connect IP:port. When Oxide plugins start throwing errors right after an update, check that the framework itself is on the current build before debugging individual plugins.
How to Set Up a Rust Server
- 1
Pick a plan from your target world size and player count
Gold 8GB fits a small clan server on a 3000 map; a modded community expecting 100+ players should start at Emerald 16GB or Xtreme 32GB.
- 2
Check out and let the server install itself
Once payment clears, RustDedicated is installed automatically and your server shows up at gamepanel.hostingmerkezi.net. The first boot takes a few extra minutes while the map is generated.
- 3
Set hostname, world size, seed and max players
Edit the startup values and server.cfg to name your server, write a description, choose the world size and seed, and set the player cap, then restart.
- 4
Grant yourself owner and lock down RCON
Run ownerid with your SteamID64 followed by server.writecfg, set a strong rcon.password and confirm your WebRCON client can connect.
- 5
Install Oxide or Carbon and upload plugins
Add your chosen framework, upload .cs plugins over SFTP or the file manager, tune their JSON configs and assign permissions to your groups.
- 6
Bring your players in
Players can find you by name under the Community or Modded tab, add you to Steam favorites, or connect directly with client.connect IP:port from the F1 console.
Frequently Asked Questions
What server owners ask us before launching a Rust server, and what they ask again on wipe day.
How much does Rust server hosting cost?
Which plan should I choose for my Rust server?
Do you support Oxide/uMod and Carbon plugins?
How long does setup take?
How do players connect to my Rust server?
What do I need to do on forced wipe day?
How do backups work?
Is my Rust server protected against DDoS attacks?
Can I upgrade my plan as the server grows?
Can I run a custom map?
Related Guides
İstanbul Location,
Maximum Performance
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
İstanbul
Turkey
Explore Our Other Services
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news
