Why Does Rust Ban on Thursdays?
Facepunch bunches monthly Rust bans into the first Thursday of each month — coinciding with the force wipe and content patch. The pattern lets cheat detection signatures trigger silently during the month, then release as a batched ban wave alongside the wipe, making it harder for cheat operators to trace which specific build version got flagged. Continuous real-time bans still happen via EAC, but the headline wave is Thursday-anchored.
The Thursday wipe cadence
Rust runs on a fixed monthly wipe schedule: every first Thursday of the month the official servers force-wipe and a content patch lands. This is the most predictable patch schedule in any major game we cover — Facepunch publishes the wipe calendar months in advance, and the community plans wipe-day raid groups around it. The Thursday cadence is the structural reason behind Rust's distinctive ban-wave pattern.
Why bans cluster on wipe Thursdays
Facepunch's continuous detection model (90.8% automated per Surviving 12 Years) flags cheaters in real time, but the headline bans are batched for tactical reasons. The pattern: a cheat's detection signature triggers during a session, the player keeps playing, and on the next first-Thursday-of-month, the ban lands alongside the wipe + content patch. The grouping makes it harder for cheat operators to attribute the detection to a specific build version because the batch includes multiple weeks of detections released simultaneously.
Why the wipe-day batching specifically
Two reasons. Reason one — tactical opacity. If Facepunch banned each cheater the moment EAC's signature fired, cheat developers could correlate detection events with their build releases and identify which specific build version got signed. By batching, the cheat operator sees a wave of bans but cannot pin down which signature caused each individual flag. Reason two — operational efficiency. Wipe-day is when Facepunch's anti-cheat staff is most engaged — they're shipping patches, monitoring server health, and reviewing edge-case appeals. Batching detections into that window concentrates the operational effort.
The pre-wipe sweep
The 24-48 hours before force wipe is also high-risk. Facepunch's pre-wipe sweep catches cheaters whose detections fired in the last week of the prior cycle. Some experienced operators recommend not playing the 24 hours before wipe Thursday — that is overly cautious but not unreasonable. The post-wipe session (Thursday afternoon onward) is also higher-risk because cheat operators are pushing updates faster than usual and Facepunch is running aggressive monitoring on the new build.
The verified 2025-2026 wave pattern
Per Facepunch's own data and Alistair McFarlane's dev tweets: April 2025 = 19,876 perm bans, May 2025 = ~19,876, June 2025 = 15,440. February 5, 2026 = Naval Update wipe + coinciding ban wave. March 6, 2026 = Shipshape Update wipe + ban wave. April 3, 2026 = Spring Clean Update + ban wave with tightened recoil heuristics. May 1, 2026 = pre-wipe sweep ahead of May 7 Upgrade Hard / Raid Harder update. The pattern is consistent across years.
Continuous bans still happen
Wipe-day batched bans are the headline waves, but EAC's real-time detection still bans accounts continuously throughout the month for clear-signature cheat detection (free public cheats, hours-old detection signatures). The continuous bans tend to hit the cheap free-cheat end of the market faster; the wipe-day batched bans tend to catch the more sophisticated paid-cheat users whose detection signatures took longer to develop.
The wipe-day operational discipline
For cheat users, the Thursday cadence creates a specific operational discipline. Pre-wipe: confirm the cheat update is queued. Post-wipe (T-0 to T+12 hours): wait for cheat status to flip back to UNDETECTED for the new game build. Don't run the previous build on the post-wipe game — that is the single most common cause of post-wipe bans because the cheat's offsets are stale and EAC reads inconsistent state. T+0 to T+72 hours: stick to known-stable settings, do not push edge-case features (Misc panel exploits like Thick Bullet, Instant Eoka, etc.) in the first 72 hours. T+1 week onward: stable operating window. Most ban-wave correlation evidence shows post-wipe waves catch users in the first 7 days.
The cluster wipe context
Most Rust cheat operators (including us) treat wipe-day as the single highest-priority engineering milestone of the month. Patches ship within 6-12 hours of the wipe-day game patch landing. Status updates post on the forum and Discord with the build version. The Rust ban wave history cluster expands every documented wipe-day wave from 2024-2026.
Pair this with
The wipe-day cadence is the most predictable scheduling factor in any major cheat market. See the Rust Cheats Complete 2026 Guide for the full ban-wave timeline, the setting up Rust cheats safely cluster for the full pre-wipe checklist, and Raw Rust for the in-house product with wipe-day patch SLA.
Related Pages
Sources
- Surviving 12 Years (Facepunch 2025 transparency) — Facepunch Studios
- Facepunch dev tweet on monthly bans — Alistair McFarlane
- Naval Update wipe announcement — Facepunch Studios
- Spring Clean Update (April 3, 2026) — Facepunch Studios
Related Questions
Depends on play pattern. For wipe-day raiders, software external cheats with World ESP and Tool Cupboard scouting deliver meaningful value at $4.99-$20/month. For Premium Servers play, you also need the $15 inventory gate cleared and a current HWID spoofer for cross-EAC protection. For casual community-server players, the cost-benefit is weaker. Free Rust cheats are not viable — they are Lumma/Vidar 2.0 infostealer payloads that drain Steam inventories worth hundreds of dollars.
Facepunch detects Rust cheaters via a four-layer stack: EAC's kernel signature scanner, server-side player culling (since May 2025) that breaks packet ESP, a server-side spray-pattern recoil analyzer (since November 2025) that catches AHK scripts, and Premium Servers' $15 Steam inventory gate that filters disposable cheat accounts. Plus 90.8% automated detection per Facepunch's 2025 transparency numbers. HackerOne paid researchers $300K+ for bug bounties.
In May 2025, Facepunch deployed server-side player culling on every official Rust server — the server stops transmitting position data for players occluded by terrain. Naive packet-stream ESP that read enemy positions from the network broke overnight. What survives is memory-residue ESP (1-3 second cache of recently-seen players), radar fusion of multiple signals, and full World ESP for loot and deployables which is unaffected because that state is server-persistent.
The best Rust cheat in 2026 is a software-based external cheat with memory-residue ESP, dynamic recoil compensation (not static AHK scripts), and a bundled HWID spoofer for cross-EAC ban protection. The May 2025 server-side culling killed naive packet ESP. The November 2025 spray-pattern analyzer killed static no-recoil scripts. Raw Rust ships dynamic recoil, six-category World ESP, and Tool Cupboard scouting overlays.
