Rust's monthly force wipe is the most reliable event in multiplayer gaming: on the first Thursday, Facepunch ships the monthly update, every map in the world resets, and a large share of a player base that peaks north of 200,000 concurrent logs in within the same couple of hours. It is also, for a server with 120 slots, the hardest day of the month.
(Blueprints are a separate question. They do not clear every month — Facepunch wipes them when progression changes and says so in the devblog beforehand. Owners who advertise a monthly BP wipe are making their own choice, not following the game's.)
The concentration problem
Force wipe rewards scale. Players want a full server on day one, because an empty wipe is a boring wipe. So everybody goes to the servers that are already big, those servers fill in minutes, and the overflow goes to the second biggest, and so on down. A small community that had a healthy 80 players in mid-cycle can wake up on wipe day with 25, because their regulars queued for something bigger.
The effect compounds. A weak wipe day means a weak first week, which means a weak mid-cycle, which means an even worse wipe day next month.
Wipe day is not a population event for small servers. It is a retention test they did not ask to take.
What smaller servers are doing about it
Three strategies show up repeatedly among the servers on the Rust server list, and they are genuinely different bets.
1. Move off the force wipe date
Wiping on a Saturday two days after force wipe, or on a completely independent weekly cycle, means you are not competing with the giants on their best day. Servers like the weekly duo and trio communities have done this for years.
- Upside: you get the players who bounced off a full 300-slot server on Thursday.
- Downside: you inherit players who already had their fresh start somewhere else on Thursday, and your first day is always slightly awkward.
2. Lean harder into a constraint
Solo-only, duo-only, no-BP-wipe, low pop by design. A constraint gives someone a reason to choose you over a bigger server that does everything.
- Upside: the constraint is the marketing, and it is defensible.
- Downside: you have to enforce it properly. An unenforced group limit is worse than no group limit, because it advertises a promise you break.
3. Schedule around a timezone rather than a date
An 18:00 CET wipe and a 19:00 UK wipe are different products. Being the best server for a specific region at a specific hour beats being the 40th best global server.
What this means if you play rather than run one
Some of this is good news. Mid-cycle on a smaller server is one of the better experiences in Rust: bases you can actually raid, groups you recognise, and admins who answer.
Practical advice:
- Do not judge a server by wipe day population. Check it on a Sunday in week two.
- Read the wipe schedule before the description. Weekly, biweekly and monthly are three different games.
- Check the group limit and whether it is enforced. A "max 3" server with a five-man roaming is not a max-3 server.
- Find out where the admins play. Staff on separate unprivileged accounts is a real signal; staff with loot access is a real warning.
The uncomfortable part
Some servers should close. There are far more Rust servers than there are Rust players to fill them, and a community running at 12 out of 150 for three months is not going to recover through better SEO. The healthier outcome — and one that happens more often than people expect — is two small communities merging their Discords and running one server properly.
That is not a tragedy. It is what a mature server list looks like: fewer entries, better ones, and a wipe day where a mid-size community can still fill its slots. If you are on the player side of this and trying to pick a cycle to settle into, the schedule that suits a solo is a different calculation from the one an owner is making.
JoinGG is a live directory of community game servers — current status, players online right now, and a copyable address for every listing.
Common questions
- Do Facepunch force wipes automatically reset blueprints every month?
- No, Facepunch does not wipe blueprints every month. Map wipes occur every monthly update, but blueprints are only cleared when progression changes, which Facepunch announces in the devblog beforehand. Server owners advertising monthly blueprint resets are making an independent choice.
- What is the best way to judge if a smaller Rust server is active?
- Check the server's population on a Sunday during its second week rather than on wipe day. Wipe day numbers heavily favor large servers, while mid-cycle counts provide a much better picture of actual community retention.
- What should a failing Rust community do if player numbers do not recover?
- Merging Discords and servers with another small community is often the best outcome. When a server continually averages low counts like 12 out of 150 players across several months, combining forces allows both to create a single, properly populated server.
Published · 4 min read