Rust wipe timer.
Set it once.

Generate your wipe timer

+server.tags "monthly" +wipetimer.wipeTimezone Europe/London +wipetimer.wipeDayofWeek 4 +wipetimer.wipeHourofDay 19

How Rust’s wipe timer works

The countdown on the laptop at the bottom of the Missile Silo counts down to your next wipe, and the server starts its end-of-wipe events (the F-15 flyovers and road Bradleys) in the last 24 hours before it. Rust works the date out from four settings:

With the defaults, monthly means the first Thursday of the month at 19:00 London, which is Facepunch’s force wipe. Weekly means every Thursday at 19:00. Biweekly means the first and third Thursday, and the wiki says a month with five Thursdays has its three-week gap split into two weeks plus one. Change the day and hour and the same rules apply to your day.

Check it worked

After a restart, run PrintWipe in the server console. It prints the frequency, timezone, day and hour it is using, the next wipe time, and the ten wipes after it. This is what it printed on our test server with the default schedule:

Wipe day of week: Thursday
Wipe hour: 19
Wipe time: 2026-11-05T19:00:00.0000000+00:00
server.tags: "monthly,vanilla"

If the dates don’t match the generator, look for a second server.tags or wipetimer line overriding the first.

Schedules the tags can’t describe

A three-day cycle, or two wipes a week, doesn’t fit monthly, biweekly or weekly. Rust has two overrides for those: wipetimer.wipeCronOverride takes a cron expression, for example "0 14 1-7,15-21 * 4" for the first and third Thursday at 14:00, and wipetimer.wipeUnixTimestampOverride takes one exact time. The timestamp override beats everything else, and Rust ignores it once it is in the past.

This page doesn’t generate overrides. Your browser filter still needs the nearest of monthly, biweekly or weekly.