Every Rust server operator eventually faces the wipe dilemma: wipe too frequently and long-term players leave, frustrated they can't maintain progress. Wipe too rarely and the server becomes dominated by entrenched clans, discouraging new players from joining at all.
The wipe schedule is the single highest-leverage configuration decision for a Rust server's population health.
Why Wipe at All?
Rust's core tension (survival, resource accumulation, raiding) depends on scarcity. After two weeks on the same map, every oil rig has been looted a hundred times, every monument camped by the same clan. The world feels exhausted. A wipe resets the playing field and reinjects the core emotional hook: starting from nothing, building something worth defending.
Additionally, entity counts accumulate across a map's lifespan. Abandoned bases, deployed items, and sleeping players all create server-side load. A fresh wipe dramatically reduces TPS load by eliminating thousands of stale entities.
The Wipe Schedule Data
Community analysis across major Rust server clusters (2024 to 2026) shows clear population patterns:
| Wipe Frequency | Peak Population | Population Decay Rate | Best Server Type |
|---|---|---|---|
| Daily/2-day | Very high first 6h | 80% gone by day 3 | Zerg/chaos, competitive PvP |
| Weekly (Thursday) | High at wipe | Moderate | Solo/Duo, casual PvP |
| Bi-weekly | Moderate at wipe | Low | Clan servers, 5x/vanilla |
| Monthly | Lower wipe peak | Very low | Building communities |
Thursday wipes synchronise with Facepunch's forced monthly wipes and create the highest wipe-day peaks.
Solo/Duo/Trio Wipe Frequency
The fastest-growing Rust server format in 2025 to 2026 is restricted player count (solo, duo, or trio max). These servers work best on bi-weekly wipes: long enough for players to build meaningful bases, short enough that no duo team can achieve map dominance permanently.
Staggered Blueprint Wipes
Consider separating your map wipe from your blueprint wipe. Blueprint wipes reset progression (research trees, workbench knowledge), while map wipes only reset the terrain and structures. Running:
- Map wipe: Every 2 weeks
- Blueprint wipe: Monthly (or quarterly for established communities)
Players who invested 30+ hours in blueprint research are far less likely to leave the community if their research carries over across map wipes.
Technical Wipe Configuration
Rust has no startup flag that wipes the server. A wipe is done with files: stop the server, then delete the right files in its identity folder (server/<identity>/).
- Map wipe: delete the
.mapfile and the.savfiles, including the.sav.1and.sav.2backups. Change the seed in your startup command if you want a new map instead of the same one regenerated. - Blueprint wipe: delete the
player.blueprints.*.dbfile as well. Leave it in place and blueprints carry over to the next map.
./RustDedicated -batchmode \
+server.hostname "Your Server Name" \
+server.identity "myserver" \
+server.seed 12345
On your own Linux machine, a cron job can run a script that stops the server, deletes those files and starts it again, for example every Thursday at 2 AM:
0 2 * * 4 /home/rust/wipe.sh
On a hosted server you usually do not get cron. With a Pterodactyl panel, which is what our Rust servers use, you can still get most of the way there: set up a schedule that warns players with a say command and stops the server at wipe time, then delete the map and save files (and the blueprint file for a BP wipe) in the file manager, change the seed and start the server again.
If you would rather not run the whole server on your own machine, see our hosted Rust servers.