Schedule a Rust Server Wipe: Map, Blueprints and Calendar
Choose a monthly, biweekly or weekly cycle, separate map and blueprint wipes, then execute and verify the reset safely.
A Rust wipe is not one single operation. A map wipe recreates the world and structures; a blueprint wipe also resets learned blueprints. The official timer informs players and drives end-of-cycle events, but it does not replace the stop, backup and controlled deletion procedure.
Choose and publish a wipe cycle
| Cycle | Best for | Trade-off |
|---|---|---|
| Monthly | Long progression and smaller communities | Larger gap between new and established players |
| Biweekly | Active communities that want regular restarts | Two launches to operate per month |
| Weekly | Fast PvP and strong fresh-wipe activity | Progress is removed very often |
Choose an exact time and timezone, publish them on Discord, the website and description, then set one schedule tag:
server.tags monthly,vanilla
Replace monthly with biweekly or weekly. Tags in the same group are mutually exclusive; publishing several schedules breaks browser filters.
Configure the official wipe timer
By default, Rust aligns its timer with force wipe: the first Thursday of the month at 19:00 Europe/London. For weekly or biweekly cycles, the browser tag and wipetimer variables define the countdown. Adapt this server.cfg example:
server.tags weekly,vanilla
wipetimer.wipeTimezone Europe/Paris
wipetimer.wipeDayofWeek 4
wipetimer.wipeHourofDay 19
Days run from 0 (Sunday) to 6 (Saturday), so 4 is Thursday. For short or exceptional schedules, the official documentation supports a Unix date or cron override. An override in the past is ignored.
The timer does not delete the world
Perform a map wipe or full wipe
Freeze activity and back up
server.save, wait for the write, stop the server and archive the whole server.identity directory. Store it off-host with date, seed, worldsize and protocol.Decide what to remove
.sav and .map files while preserving blueprint files. For a full/BP wipe, also remove the player blueprint file. Do not reset config, bans or admins unless intended.Choose the next map
server.seed, server.worldsize and level before startup. A new seed or size creates a different map; document values so the cycle is reproducible.Update and restart
Server startup complete.Validate before opening
A force wipe may increment the save protocol when an old world is no longer compatible. Facepunch warns against renaming an old .sav to bypass that rule; it can produce an inconsistent world.
Prevent accidental wipes
Never remove files while the process is running. Work inside the exact identity directory: several instances can share Rust binaries while keeping separate worlds. After restart, compare the log and new file timestamps. Keep at least one tested restore point from the previous cycle.
Use the Rust backup and update guide for the complete maintenance sequence. The ports and browser guide helps restore visibility without changing the address.
Automate Rust wipes without losing control
Compare Rust servers with scheduled backups, wipe tasks and a console.
Frequently asked questions
What is the difference between a map wipe and BP wipe?
Does the Server Wipe Timer perform the wipe?
When is the default monthly timer?
Sources: Server Wipe Timer, Server Browser Tags and Rust identity files.
Ready to launch your Rust server?
Here are the best Rust hosting deals right now, promo codes included. Still unsure? Our quiz finds the ideal host for you in under 2 minutes.
My box 12
Minestrator
Specifications
Compatible games
Features
- ✓DDoS Protection
- ✓Backups
Wood
Shockbyte
Specifications
Compatible games
Features
- ✓DDoS Protection
- ✓Oxide mod support
- ✓Instant Setup
- ✓24/7 Support
Rust
OptiNAS
Specifications
Compatible games
Features
- ✓Environ 30 joueurs
- ✓Minimum : 6 vCPU et 16 Go de RAM
- ✓Conseillé : 6 vCPU et 16 Go de RAM
- ✓Plugins et mods possibles selon le jeu
- +2 more features