Unturned Starter · 2 GB
€2.14 / month
- vCPU
- 2 cores
- RAM
- 2 GB
- Storage
- 30 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
SURVIVAL · PC
Unturned combines map choice, zombie and item density, player structures, Rocket plugins, and Workshop assets.
€2.14 / month
€3.03 / month
€4.10 / month
€5 / month
€7.14 / month
Busy settlements, many vehicles, and placed objects can create more persistent-world work than a plain vanilla map.
The first resource profile for a controlled launch and measurement baseline.
A middle profile to assess as community and content workload grows.
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
Evaluate CPU, memory, and storage options against the expected game workload.
Combat in one city concentrates network and entity events, while separate base regions expand save coverage.
Measure processor peaks and game-loop response during a busy session.
Track peak memory use together with growth headroom.
Measure storage behaviour across saves, logs, and backups.
Measure actual mod, plugin, and script workload separately from extension count.
Track world size, active regions, and persistent-data growth together.
Evaluate concurrent-player distribution, activity, and content workload together.
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | Combat in one city concentrates network and entity events, while separate base regions expand save coverage. | Measure a busy session |
| Game activity | Busy settlements, many vehicles, and placed objects can create more persistent-world work than a plain vanilla map. | Repeat the peak scenario |
| World / save growth | Barricades, structures, vehicles, and player data expand the save; apply cleanup while retaining recoverability. | Track save and restore duration |
Estimate starting capacity from your player and world goals.
Estimated CPU, memory, storage, and a suitable resource profile appear here.
Control Workshop collections, asset dependencies, and Rocket plugin versions; opening a world with missing assets is risky.
Mod compatibility can vary by game and server-software release.
Audit map, difficulty, loot and zombie rules, permission groups, plugin order, and access lists.
After deployment, manage Unturned processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up Unturned saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to Unturned configuration, logs, and managed content directories; stop the relevant process before replacing active files.
List the map, asset collection and plugins you intend to use. Measure an actual session with developed bases and vehicles, rather than using a basic starting map as the capacity reference for every content set.
Evaluate a concentrated session separately from one where players occupy different bases. Network and server work can peak differently, so connection count alone should not decide the plan.
Preserve the working save and resolve the map, collection and dependencies first. Load a copy to check important objects before adopting the new setup, and confirm installation scope separately from resource rental.
Separate world data you want to keep from unnecessary logs, and test cleanup on a backed-up copy. If the retained world still reaches CPU, memory or storage limits, compare plans for that requirement.
Keep player, vehicle and structure data along with permission groups, plugin order and game rules. On restart, check that the intended map and access list are in use.
Contact support for ordering details and special requirements.