2/200
Last checked 41 s ago
Wiped 2 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
274 ms · Chicago
Last checked 4 m ago
0 / 10 players
Procedural Map
5x 11 days live Avg ping 235.2 ms Avg jitter 14.6 ms Wipe cycle 5.1 ±4 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 47.120.40.27:28015
First seen 22.09.2026
Last wipe: (2 d ago)
| Wiped | Days since previous |
|---|---|
| 9.2 | |
| 1.1 | |
| — |
Wipe timing behind this data is sometimes inferred rather than confirmed, so daily figures right around a wipe boundary can land on the wrong day. Accuracy improves over time as detection gets more precise.
Highest peak 4 Oct 2 · 10:13 UTC Median daily peak 2 (median of daily peaks, not average population)
Observed daily peak
12 full · 0 partial · 0 offline · 79 no data
Each line follows one wipe cycle from the moment it started, lined up by days since that wipe rather than by calendar date — so you can compare how well this server held onto its population after different resets, independent of when each one happened.
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 274 ms | 1 | |
| Offline | 268 ms | — | |
| Online | 232 ms | 2 | |
| Online | 232 ms | 2 | |
| Online | 228 ms | 0 | |
| Online | 235 ms | 0 | |
| Online | 235 ms | 2 | |
| Online | 239 ms | 0 | |
| Online | 233 ms | 0 | |
| Online | 235 ms | 0 | |
| Online | 242 ms | 1 | |
| Online | — | 1 | |
| Online | 231 ms | 3 | |
| Online | 232 ms | 2 | |
| Online | 253 ms | 1 | |
| Online | 235 ms | 1 | |
| Online | 231 ms | 2 | |
| Online | 237 ms | 0 | |
| Online | 234 ms | 0 | |
| Offline | — | — | |
| Online | 234 ms | 1 | |
| Offline | 248 ms | — | |
| Offline | 237 ms | — | |
| Online | — | 0 | |
| Online | 249 ms | 0 | |
| Online | 251 ms | 0 | |
| Online | — | 1 | |
| Online | 240 ms | 0 | |
| Online | 241 ms | 0 | |
| Online | 234 ms | 0 | |
| Online | 234 ms | 0 | |
| Offline | — | — | |
| Online | 241 ms | 0 | |
| Online | 228 ms | 0 | |
| Online | 228 ms | 1 | |
| Offline | 229 ms | — | |
| Online | 242 ms | 1 | |
| Online | 227 ms | 0 | |
| Online | 233 ms | 0 | |
| Online | 234 ms | 0 | |
| Online | 232 ms | 1 | |
| Online | 241 ms | 0 | |
| Online | — | 1 | |
| Online | 237 ms | 0 | |
| Online | — | 1 | |
| Offline | 267 ms | — | |
| Online | 237 ms | 0 | |
| Online | 301 ms | 0 | |
| Online | 232 ms | 0 | |
| Online | 228 ms | 0 |
2/200
Last checked 41 s ago
Wiped 2 d ago
Procedural Map

0/200
Last checked 4 m ago
Wiped 2 d ago
Procedural Map
A wipe resets a server's map and usually player progress too — bases, resources, and blueprints, unless the server keeps blueprints through wipes (shown here as "No BP wipe"). Most servers wipe on a regular schedule, often weekly.
Facepunch pushes a mandatory update on the first Thursday of each month that requires every Rust server to wipe, regardless of its own schedule — a "force wipe," distinct from a server's regular map wipe.
The "Next wipe" time above is extracted from the server's own published schedule. "High confidence" means the server stated an explicit date or time; "Predicted" means it's estimated from the server's typical cadence and isn't guaranteed.
Copy the server address above, open Rust's in-game console with F1, and run client.connect followed by the address — or connect directly through Steam's server browser using the same address.