Rust Autowipe Server HostingRust Autowipe Server Hosting
For Rust servers that wipe often: list what gets deleted once, then move to a fresh map with a single reinstall every wipe day.
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 Autowipe Plan Is Right for You?
Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Gold 8GB | Weekly wipes, 3000 map, 20–30 playersShort wipe cycles cap entity buildup, making this an economical start for a small community. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | Weekly/biweekly wipes, 30–50 playersRoom for kit, teleport and economy plugins plus the wipe-day rush. | 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 playersBalanced headroom for mid-sized communities on a biweekly cycle. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | 100+ players on wipe day, many pluginsSix vCores absorb the heavy building and gathering of a new map's first hour. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | Large map, 150+ players, monthly full wipesKeeps big communities well clear of the memory ceiling even on long wipe cycles. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
Why TheCrewHost for Rust Autowipe?
On a server that wipes often, the most tedious job is the file cleanup, so this environment turns it into a repeatable step.
Wipe by reinstall
Set Regen Server to 1 and trigger a reinstall from the panel: server files are updated and every path in Files to Remove is deleted in one pass.
An editable removal list
The list is space-separated file paths and supports wildcards, so one entry catches database files whose version number changes between Rust updates.
A new map every wipe
Leave World Seed at 0 and a random seed is generated and stored during the reinstall, so players spawn on a different island each wipe.
Reset plugin data too
Add kit cooldowns, home teleport points, economy balances or playtime trackers to the list and they are cleared together with the map.
A safety backup first
Beyond automatic backups, take a manual backup from the panel right before wiping. If the wrong file made the list, restore the old world within minutes.
Help with your wipe list
Unsure whether a file belongs on the list? Ask our 24/7 support team through a ticket, live chat, Discord or WhatsApp before wipe day.
Rust Autowipe server hosting starts at $11.00 (₺440.00) per month and gives you the same RustDedicated server as our standard Rust plans, plus extra settings built around wiping. You keep a list of files to remove in the panel; with Regen Server enabled, reinstalling the server updates the game files, deletes everything on that list and writes a new random seed. Weekly and biweekly wipe communities stop hunting through folders every time. It all runs in İstanbul on a Ryzen 9 9950X with NVMe storage, and you can add Oxide or Carbon plugin data files to the same list so plugin state resets alongside the map.
What is a Rust Autowipe server and how is it different?
In game, a Rust Autowipe server is identical to a standard Rust server: the same RustDedicated build, the same convars, the same Oxide/uMod and Carbon compatibility. The difference is how wipes happen. Normally, every wipe means stopping the server, opening the identity folder and deleting the .map and .sav files, player databases and plugin data one by one. Here you write those paths into a list once.
On wipe day you keep Regen Server enabled and reinstall the server from the panel. The reinstall updates the server files, removes whatever is on the list and, if World Seed is 0, saves a fresh random seed. When the server boots, players land on a new map.
To be clear about scope: this setup does not run on a clock. You decide when to wipe and you start the reinstall. What it gives you is a wipe that runs the same way every time, with nothing forgotten. If you prefer to handle wipes by hand or run something highly custom, our standard Rust hosting page may suit you better.
Which files does the default wipe list remove?
The default list covers a map wipe. From server/rust it removes the player.deaths, player.identities and player.states databases, player.tokens.db, and the procedural map .map and .sav files. It also clears data files for a few widely used plugins: Kits data, NTeleportation homes, ServerRewards player data and PTTracker playtime.
The notable omission is the player.blueprints databases, so a wipe with default settings keeps everyone's learned blueprints. For a full BP wipe, add server/rust/player.blueprints.*.db to the list; the wildcard matches whatever version number the file name carries.
Some files should never go on the list. Oxide's user and group data files under oxide/data hold your VIPs, admins and every permission you granted; delete them and your whole permission setup starts from zero. server.cfg and users.cfg hold persistent settings and belong off the list as well. Removing entries for plugins you do not run keeps the list readable when you come back to it next month.
Which wipe schedule fits your server?
The forced wipe on the first Thursday of the month is fixed for everyone; the schedule in between depends on the kind of server you run. Weekly wipes are standard on high-rate, fast-paced servers where players build, raid and move on within a few days. Biweekly wipes suit mid-tempo servers such as 2x, giving clans time to develop their bases. Monthly-only wipes are for near-vanilla servers with players who enjoy a long game.
A common blueprint pattern is to keep BPs through the in-between wipes and do a full wipe on forced wipe day. In practice that means adding the player.blueprints entry only on the first Thursday and taking it out again afterward.
Timing matters as much as frequency. For a community playing from Türkiye, an evening wipe lets most players start together, which keeps the first hours lively. Whatever you pick, put it in the server description and on your Discord and stick to it; a predictable schedule is one of the simplest ways to earn player trust.
What does a wipe day look like, step by step?
Start with a backup. Create a manual one from the panel; if a config file slipped onto the list by mistake, this is what saves you. Then announce the wipe in game and on Discord and stop the server.
Next, check your settings. Regen Server should be 1, World Seed should stay 0 if you want a random map, and Custom Map URL should be empty unless you run a custom map, because when it is filled the seed is not used at all. If this is a BP wipe, add the blueprint entry to the list. When everything looks right, start the reinstall from the panel.
Once it finishes, start the server and watch the console as the new map generates. On forced wipe day, confirm the current Oxide or Carbon build is in place and that plugins load without errors. Finally, set Regen Server back to 0. If you leave it on, a routine reinstall to fix an unrelated issue mid-month will wipe the server too.
How much RAM does a frequently wiped server need?
Frequent wipes have a useful side effect. Since accumulated structures are what drive Rust memory usage up, a weekly-wipe server peaks lower than a comparable monthly-wipe server, and you can sometimes run one plan lower for the same player count.
The wipe itself, however, is intense. In the first hour on a new map most of your players connect at once, gather and build; size the server for that first-hour concurrency, not for a quiet Tuesday.
As a rough guide: Gold 8GB handles a weekly-wipe 3000 map with 20 to 30 players, Platinum 10GB takes you to around 50, and Diamond 12GB covers a 3500 to 4000 map with 50 to 80 players. For wipe-day crowds over 100 with a long plugin list, the six-vCore Emerald 16GB is our pick, and Xtreme 32GB suits large-map communities. Upgrades can happen between wipes, and your world and wipe list come along unchanged.
What are the most common autowipe mistakes?
The most frequent one is wiping the map but not the plugin data. If home teleport data survives, players teleport to coordinates from the old map, which on the new one might be open ocean or the inside of a cliff. If kit cooldowns survive, fresh players cannot claim their starter kit.
The second is typing a fixed number into World Seed and forgetting about it. The reinstall still deletes the files, but the server regenerates the exact same island every time. The third is expecting a procedural map while the Custom Map URL field still holds a link.
The fourth is putting permission files on the list; watching every VIP and moderator lose their rights after a wipe does not look good to a community. The fifth is leaving Regen Server on. Every one of these is avoided by reading the list once before wipe day and taking a backup.
How to Set Up a Rust Autowipe Server
- 1
Size the plan for wipe-day concurrency
Frequent wipes keep memory peaks lower, but the first hour on a new map is the real test; choose between Gold 8GB and Xtreme 32GB with that crowd in mind.
- 2
Complete checkout and let the install run
After payment, RustDedicated installs automatically and your server appears at gamepanel.hostingmerkezi.net; the first boot adds a few minutes of map generation.
- 3
Set the server name, world size and player cap
Fill in hostname, description, world size and max players in the startup values; leave World Seed at 0 if you want a random map each wipe.
- 4
Tailor the removal list to your plugins
Go through the default list, add the data files of plugins you actually run, remove the rest, and decide when the player.blueprints entry should be on it.
- 5
Test your first wipe with a backup in place
Back up from the panel, set Regen Server to 1 and reinstall. Once the new seed is live and plugins load, set Regen Server back to 0.
- 6
Publish your schedule and invite players
Put your wipe schedule in the server description; players find you by name in the browser or join with client.connect IP:port from the F1 console.
Frequently Asked Questions
Answers for owners who wipe their Rust server from a file list.
How much does a Rust Autowipe server cost?
Does the autowipe run by itself at a set time?
Are blueprints wiped with the default settings?
Which plan should I pick, and do frequent wipes lower RAM needs?
Do Oxide and Carbon plugins work here?
How long does setup take, and how long does a wipe take?
How do players reconnect after a wipe?
What if I deleted the wrong file?
Am I protected against DDoS attacks on wipe night?
Can I upgrade when my community grows?
İ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
