Rust Wipe Schedule 2026–27: Every Forced Wipe Date and Time

The Rust wipe schedule is simple once you know the rule: Facepunch wipes every server on the first Thursday of the month at 19:00 UK time. The next forced wipe is Thursday 5 November 2026. Below are all the dates to December 2027, what each wipe erases and how to plan your own on our Rust server hosting.

• Forced wipe: the first Thursday of every month at 19:00 London time, which is 20:00 in Madrid, Paris or Berlin all year round.
• Next dates: 5 November 2026, then 3 December 2026 and 7 January 2027.
• What it erases: the map, on every server in the world. Blueprints only go when Facepunch says so, or when the server owner chooses to.
• Your own cadence: a community server can wipe weekly, every two weeks or monthly on top of the forced wipe.
• On 1up: a scheduled task wipes the map, or the map and the blueprints, on the day and at the hour you pick.

1. When is the next Rust forced wipe?

Facepunch's official wiki puts it in one line on its Server Wipe Timer page: the monthly default is the «First Thursday every month at 19:00 (London time)». The monthly update and the forced wipe arrive together, and the devblog usually goes up a few minutes before. The last three updates show it: Livestock on 1 October 2026, Breach and Clear on 3 September and Power Trip on 6 August, all first Thursdays, all posted on Steam shortly before 19:00 UK time.

London time means GMT in winter and BST in summer, so the hour in UTC moves while the hour on a British clock stays at 19:00. Spain, France, Germany and the rest of the CET zone change their clocks on the same nights as the UK, so for us the wipe is always at 20:00 CET or CEST.

2. Rust forced wipe dates, November 2026 to December 2027

Clocks go forward on 28 March 2027 and back on 31 October 2027, which is why April to October read 18:00 in UTC. One date deserves a check closer to the day: 4 November 2027 falls in the week when the UK is back on GMT but the United States is still on summer time. In October 2025, Facepunch warned server owners that «patches will be brought forward an hour» until other time zones change their clocks too. If they do the same in 2027, that wipe lands at 18:00 GMT, 19:00 CET.

Facepunch can still move a date. Look out for their devblog and Steam news in the last week of each month; we refresh this table every month.

3. Map wipe vs blueprint wipe

A Rust server keeps two kinds of progress, and the official wiki's server guide names the files that hold them:

• The map lives in the .sav file: «all map data and entities, player buildings, deployables and more». A map wipe throws away every base, box and item and starts a fresh island.
• Blueprints live in player.blueprints: everything each player has learned to craft. A blueprint wipe (BP wipe) sends everyone back to the starting recipes.

The forced wipe is a map wipe. The wiki explains that the number in the save file name is the protocol version, that it «increases at a forced wipe forcing your server to create a new one», and that «generally it only happens with the sav file because they only force a map wipe». A blueprint wipe, it adds, means deleting the blueprints file as well. It also warns that renaming an old save to dodge the forced wipe is «dangerous and ill-advised».

Facepunch has forced a blueprint wipe on occasion. With the Pivot or Die update on 6 November 2025 it wrote «Today, we're wiping all Blueprints, wiping all servers», noting that most servers, its own included, had stopped blueprint-wiping. On whether that becomes monthly, it said «Maybe. We're not committing to anything yet.» None of the 2026 update notes we read announced another forced blueprint wipe, so treat the blueprint wipe as your choice unless the month's devblog says otherwise.

4. Wipes on community and modded servers

Between forced wipes, each server owner sets the rhythm. Official and partner servers already show the range: when Facepunch launched Premium servers in March 2025, it listed some on monthly map wipes and community-run ones on weekly map wipes, and noted that community officials «may have their own separate blueprint wipe schedules».

Common patterns:

• Monthly: the forced wipe only. Long games, big bases, fewer resets.
• Every two weeks: a mid-month wipe plus the forced one.
• Weekly: a fresh start every Thursday, popular with groups that play hard on the first days.
• Blueprints: some servers wipe them on every forced wipe, some once a month, some never.

Rust also has an in-game wipe timer, the countdown at the Nuclear Missile Silo, and the wiki says the server starts its endgame events 24 hours before a wipe. Both follow the server's wipetimer settings, whose default matches the forced wipe. Our panel does not expose those settings yet, so on a custom cadence the in-game countdown can disagree with your own schedule.

Modded servers have one extra step. On 1up, the Oxide and Carbon templates download the current Oxide or Carbon build at every start, but the framework itself needs an update for each new Rust version. If plugins fail right after a forced wipe, wait for the new Oxide or Carbon release and restart. Plugin data in oxide/data survives our map wipes, so clear it yourself if a plugin keeps per-wipe stats.

5. How to schedule a Rust wipe on 1up

Our Rust servers install the current Rust build from Steam every time they start, so a restart after Facepunch's patch is what brings the update in. The wipe itself is a scheduled task:

1. Open your server and go to Schedule, then + New task.
2. Under What should it do?, choose Wipe. Under What gets erased?, pick Map only or Map and blueprints.
3. Pick the frequency. Weekly with Thursday ticked gives a weekly wipe. For the first Thursday of each month, choose Cron and enter 0 21 1-7 * 4: on our panel, a day range and a weekday must both match, so that line runs only on the Thursday that falls between the 1st and the 7th. For the first and third Thursdays, use 0 21 1-7,15-21 * 4.
4. Check the time zone shown next to Time in the form. Your account's time zone is used, and the example above means 21:00 there.
5. Create the task.

When it runs, the server stops, the map files (.map and .sav) are deleted from the server folder, plus the player.blueprints files if you chose both, and the server starts again on a new map. If the server is off at that moment, the task is skipped and the panel says so.

Three tips for forced-wipe day:

• Run it after the patch. Set the wipe an hour after the update, as in the example, so the restart installs the new build. A server still on the old version refuses players who have already updated.
• Warn your players. The wipe task does not post anything in chat. Add a Message task a few minutes earlier, for example 45 20 1-7 * 4.
• Keep a backup. A Backup task before the wipe keeps the last map, in case you need to roll back.

The Activity view of the Console also shows a countdown to the next forced wipe.

6. What Rust needs on 1up

Rust needs at least 8 GB of RAM and 25 GB of disk to generate and serve its map, and we recommend 16 GB. With the prices on our pricing page:

• Studio (€24.99/month): 12 GB of RAM, 75 GB of disk, 40 player slots and 30 backups. Enough for a small community map with room for scheduled wipes and backups.
• Ultra (€60/month): 28 GB of RAM, 100 GB of disk and unlimited slots, for large maps and busy servers.

You pick Vanilla, Oxide or Carbon when you create the server, and set the map, seed and world size in Settings. Changing the map forces a map wipe, and the seed is only used when a new world is created.

Verified against Facepunch's announcements and official wiki, 2026-10-04.

Change log

• 2026-10-04: first version, after the Livestock update of 1 October 2026.