Rust Recommended
€7.14 / month
- vCPU
- 4 cores
- RAM
- 8 GB
- Storage
- 100 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
SURVIVAL · PC
Rust Game Server
Explore server rental options for your Rust community. Compare resources for map size, player target and plugin setup, including room for saves that grow through the wipe cycle.
Choose a processor family
AMD Ryzen 9 9950X3D
Rust Performance · 12 GB
€12.49 / month
- vCPU
- 6 cores
- RAM
- 12 GB
- Storage
- 160 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Rust Performance · 16 GB
€17.85 / month
- vCPU
- 8 cores
- RAM
- 16 GB
- Storage
- 200 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Rust High Resource · 24 GB · Ryzen 9950X3D
€23.20 / month
- vCPU
- 10 cores
- RAM
- 24 GB
- Storage
- 240 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
Intel Xeon Platinum 8160
Rust High Resource · 24 GB · Xeon Platinum
€15.17 / month
- vCPU
- 8 cores
- RAM
- 24 GB
- Storage
- 140 GB SSD
- Processor
- Intel Xeon Platinum 8160
- Location
- Turkey
More features
- Traffic
- Unlimited
Rust High Resource · 32 GB
€20.53 / month
- vCPU
- 8 cores
- RAM
- 32 GB
- Storage
- 160 GB SSD
- Processor
- Intel Xeon Platinum 8160
- Location
- Turkey
More features
- Traffic
- Unlimited
Rust High Resource · 48 GB
€30.34 / month
- vCPU
- 8 cores
- RAM
- 48 GB
- Storage
- 200 GB SSD
- Processor
- Intel Xeon Platinum 8160
- Location
- Turkey
More features
- Traffic
- Unlimited
Resource selection
Choose Your Rust Server Plan
Dense building areas, automation, dropped items, and world events increase entity processing; measure early-wipe exploration separately from late-wipe base density.
Rust Recommended
The first resource profile for a controlled launch and measurement baseline.
- Processor
- AMD Ryzen 9 9950X3D
- vCPU
- 4
- RAM
- 8 GB
- Storage
- 100 GB NVMe SSD
Rust High Resource · 24 GB · Xeon Platinum
A middle profile to assess as community and content workload grows.
- Processor
- Intel Xeon Platinum 8160
- vCPU
- 8
- RAM
- 24 GB
- Storage
- 140 GB SSD
Rust High Resource · 48 GB
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
- Processor
- Intel Xeon Platinum 8160
- vCPU
- 8
- RAM
- 48 GB
- Storage
- 200 GB SSD
Evaluate CPU, memory, and storage options against the expected game workload.
Player load
How player count affects resources
More concurrent players add network state, inventory, combat, and construction interaction. A large fight can create a higher peak than routine gathering.
-
Single-core strength
Measure processor peaks and game-loop response during a busy session.
-
RAM
Track peak memory use together with growth headroom.
-
NVMe / SSD storage
Measure storage behaviour across saves, logs, and backups.
-
Mod and script density
Measure actual mod, plugin, and script workload separately from extension count.
-
World / map size
Track world size, active regions, and persistent-data growth together.
-
Player scenario
Evaluate concurrent-player distribution, activity, and content workload together.
Detailed planning notes
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | More concurrent players add network state, inventory, combat, and construction interaction. A large fight can create a higher peak than routine gathering. | Measure a busy session |
| Game activity | Dense building areas, automation, dropped items, and world events increase entity processing; measure early-wipe exploration separately from late-wipe base density. | Repeat the peak scenario |
| World / save growth | Bases and placed entities accumulate through a wipe; review optimization or a larger profile when save duration, garbage collection, and tick delay deteriorate together. | Track save and restore duration |
CAPACITY ESTIMATE
Estimate Resources for Your Rust Server
Estimate starting capacity from your player and world goals.
Capacity summary
Estimated CPU, memory, storage, and a suitable resource profile appear here.
Mod / plugin level
Mods, plugins, and additional content
Oxide or uMod plugins may use commands, hooks, data files, and scheduled tasks. Measure hook duration and stored data instead of relying on a plugin count.
Mod compatibility can vary by game and server-software release.
Administration
Administration and server settings
Record map seed and size, decay, gather rules, entity limits, save interval, and plugin permissions as part of the wipe policy.
Installation and management
After deployment, manage Rust processes, version changes, and settings that require restarts in controlled maintenance windows.
Backups
Back up Rust saves, configuration, and additional-content data as separate restore points before changes.
File access
Limit file access to Rust configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Frequently asked questions
Rust
Where should I start when choosing a Rust plan?
Decide on map size, target community and vanilla or plugin-based play. Compare resources for the later stages of a wipe as bases and saves grow, not just for a freshly reset map.
Is an empty post-wipe map a useful capacity test?
It is not enough. Settlements, dropped items and large fights change demand at the same player count. Include busy sessions later in the wipe cycle when assessing capacity.
Does plugin count tell me how many resources I need?
Not on its own. A plugin with frequent hooks or large data files behaves differently from several low-cost plugins. Test changes individually to identify their actual impact.
When should I consider a larger Rust plan?
Check unnecessary logs, retention and expensive plugin work first. If save time or tick delay still rises alongside a resource limit during busy sessions, compare plans with a more suitable CPU, memory or storage allocation.
What should I preserve before a wipe or settings change?
Back up the saves you intend to retain, configuration and plugin data separately. Explain the wipe scope to your community and check that the intended data set can be restored before proceeding.
NEXT STEP
Choose Your Rust Server Plan
Contact support for ordering details and special requirements.