1/200
Last checked 2 m ago
Wiped 2 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
227 ms · Chicago
Last checked 1 m ago
12 / 100 players
Procedural Map
17 days live Avg ping 217.9 ms Avg jitter 30.6 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 202.189.23.187:28015
First seen 16.09.2026
Last wipe: (2 d ago)
| Wiped | Days since previous |
|---|---|
| 28 | |
| — |
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 12 Sep 26 · 00:02 UTC Median daily peak 12 (median of daily peaks, not average population)
Observed daily peak
8 full · 0 partial · 0 offline · 0 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 |
|---|---|---|---|
| Offline | 223 ms | — | |
| Offline | 219 ms | — | |
| Offline | 217 ms | — | |
| Offline | 221 ms | — | |
| Offline | — | — | |
| Offline | 211 ms | — | |
| Offline | 186 ms | — | |
| Offline | 222 ms | — | |
| Offline | 186 ms | — | |
| Offline | 185 ms | — | |
| Offline | 218 ms | — | |
| Offline | 423 ms | — | |
| Offline | 184 ms | — | |
| Offline | 227 ms | — | |
| Offline | 221 ms | — | |
| Offline | 189 ms | — | |
| Offline | — | — | |
| Offline | 222 ms | — | |
| Offline | 206 ms | — | |
| Offline | 216 ms | — | |
| Offline | — | — | |
| Offline | 211 ms | — | |
| Offline | 219 ms | — | |
| Offline | 244 ms | — | |
| Offline | — | — | |
| Offline | 220 ms | — | |
| Offline | 221 ms | — | |
| Offline | 421 ms | — | |
| Offline | 215 ms | — | |
| Offline | 227 ms | — | |
| Offline | 213 ms | — | |
| Offline | 235 ms | — | |
| Offline | 212 ms | — | |
| Offline | 216 ms | — | |
| Offline | 208 ms | — | |
| Offline | 215 ms | — | |
| Offline | 187 ms | — | |
| Offline | 221 ms | — | |
| Offline | 214 ms | — | |
| Offline | 236 ms | — | |
| Offline | 240 ms | — | |
| Offline | 187 ms | — | |
| Offline | 229 ms | — | |
| Offline | 218 ms | — | |
| Offline | 239 ms | — | |
| Offline | 218 ms | — | |
| Offline | 209 ms | — | |
| Offline | 221 ms | — | |
| Offline | 187 ms | — | |
| Offline | 213 ms | — |
1/200
Last checked 2 m ago
Wiped 2 d ago
Procedural Map

0/200
Last checked 7 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.