2/200
Last checked 7 m ago
Wiped 2 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
200 ms · Chicago
Last checked 9 m ago
0 / 200 players
Procedural Map
45 days live Avg ping 196.7 ms Avg jitter 12.2 ms Wipe halving: 2 days Wipe cycle 9.3 ±1.6 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 110.42.9.116:28020
First seen 19.08.2026
Last wipe: (2 d ago)
| Wiped | Days since previous |
|---|---|
| 7.1 | |
| 10.2 | |
| 10.8 | |
| — |
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 Sep 22 · 10:53 UTC Median daily peak 1 (median of daily peaks, not average population)
Observed daily peak
30 full · 0 partial · 0 offline · 1 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 | 200 ms | 1 | |
| Online | 206 ms | 0 | |
| Online | — | 0 | |
| Online | 198 ms | 0 | |
| Online | 204 ms | 0 | |
| Online | 190 ms | 0 | |
| Online | 195 ms | 0 | |
| Online | 190 ms | 1 | |
| Online | 188 ms | 1 | |
| Online | 201 ms | 1 | |
| Offline | 202 ms | — | |
| Online | 202 ms | 0 | |
| Online | 205 ms | 1 | |
| Offline | 195 ms | — | |
| Online | 196 ms | 2 | |
| Online | 187 ms | 1 | |
| Online | 181 ms | 2 | |
| Online | 192 ms | 0 | |
| Online | 190 ms | 1 | |
| Online | 189 ms | 1 | |
| Online | 183 ms | 1 | |
| Offline | — | — | |
| Online | 184 ms | 1 | |
| Offline | 203 ms | — | |
| Online | — | 1 | |
| Offline | — | — | |
| Online | 203 ms | 1 | |
| Online | 181 ms | 0 | |
| Online | 182 ms | 0 | |
| Online | 198 ms | 0 | |
| Online | 206 ms | 0 | |
| Offline | 188 ms | — | |
| Offline | 192 ms | — | |
| Online | 190 ms | 0 | |
| Offline | 191 ms | — | |
| Online | 198 ms | 0 | |
| Online | 196 ms | 0 | |
| Online | 189 ms | 0 | |
| Offline | 184 ms | — | |
| Online | 181 ms | 0 | |
| Online | 206 ms | 0 | |
| Offline | 203 ms | — | |
| Online | 200 ms | 0 | |
| Online | 214 ms | 1 | |
| Online | 213 ms | 0 | |
| Online | 241 ms | 0 | |
| Online | — | 0 | |
| Online | 201 ms | 0 | |
| Online | 203 ms | 0 | |
| Online | 200 ms | 0 |
2/200
Last checked 7 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.