Skip to content
Rust

Documentation: Rust wipe planner

Wipe planner for Rust servers: computes upcoming dates of the force wipe (first Thursday of the month, editable UTC time) or of a weekly/biweekly wipe in your time zone, flags BP wipes and gives a map-file deletion script to adapt.

Last updated: 10/9/2026

Open the tool

A Rust server has to be wiped (map reset) at least at every Facepunch force wipe, which ships on the first Thursday of the month. This tool computes the upcoming dates in your time zone and prepares a cleanup script.

How to use the tool

  1. Choose the mode: monthly force wipe, weekly or biweekly wipe.

  2. Enter your IANA time zone (e.g. Europe/Paris), day and time; check the force wipe UTC time on Facepunch's site.

  3. If needed, set a BP wipe every N wipes, then read the calendar.

  4. Copy the calendar for your community and adapt the deletion script before using it, with the server stopped.

What is computed and what to verify

The force wipe date is computed as the first Thursday of each month, at an adjustable UTC time (19:00 by default). The exact time could not be confirmed on an official source: check it on Facepunch's site or the wiki's “Server Wipe Timer” page before announcing a date. The script deletes proceduralmap.*.map and proceduralmap.*.sav* in server/<identity>; file names (including player.blueprints.*.db for blueprints) may change, so back up and check them on your version.

Frequently asked questions

Must I wipe at every force wipe?
Monthly updates can make old saves incompatible: plan a map wipe at each force wipe and follow Facepunch's announcements.
Is my data sent anywhere?
No: everything is computed in your browser and only your settings are stored locally.
Screenshot of the Launch command generator toolRustOpen access
Generate your Rust server launch script: network, RCON, map, seed and rules.
LaunchConfigurationOpen
Documentation
Rust
RustOpen access
Generate your Rust server.cfg: name, slots, save interval, PvE, decay, stability and RCON.
Configurationserver.cfgOpen
Documentation
Rust
RustSign-in required
Build Oxide/uMod groups, members and permissions: ready-to-paste oxide.group, oxide.usergroup and oxide.grant commands, with import.
PermissionsOxideuModOpen
Documentation
Rust
RustOpen access
Estimate the population that suits a Rust map size (1000-6000), validate the seed and copy the launch arguments.
MapCalculatorOpen
Documentation
Rust
RustSign-in required
Compose Rust kits (items, amounts, containers, cooldown, permission) and export clean JSON to adapt to your kits plugin.
KitsPluginsJSONOpen
Documentation
Rust
RustSign-in required
Edit and validate Oxide/uMod and Carbon plugin JSON config files: raw JSON, fields, formatting.
PluginsJSONValidationOpen
Documentation