
1/125
Last checked 1 m ago
Wiped 2 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
167 ms · Chicago
Last checked 6 m ago
0 / 10 players
Procedural Map
46 days live Avg ping 172.9 ms Avg jitter 4.5 ms Wipe cycle 29.2 ±1.2 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 14.8.115.32:28885
First seen 18.08.2026
Last wipe: (2 d ago)
| Wiped | Days since previous |
|---|---|
| 28 | |
| 30.3 | |
| — |
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 0 Sep 4 Median daily peak 0 (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 |
|---|---|---|---|
| Offline | 171 ms | — | |
| Offline | 171 ms | — | |
| Offline | 174 ms | — | |
| Offline | 174 ms | — | |
| Offline | 173 ms | — | |
| Offline | 172 ms | — | |
| Offline | 174 ms | — | |
| Offline | 180 ms | — | |
| Offline | 176 ms | — | |
| Offline | 178 ms | — | |
| Offline | 166 ms | — | |
| Offline | 173 ms | — | |
| Offline | 172 ms | — | |
| Offline | 174 ms | — | |
| Offline | 172 ms | — | |
| Offline | 164 ms | — | |
| Offline | 180 ms | — | |
| Offline | 173 ms | — | |
| Offline | 172 ms | — | |
| Offline | 176 ms | — | |
| Offline | 176 ms | — | |
| Offline | 166 ms | — | |
| Offline | 177 ms | — | |
| Offline | 163 ms | — | |
| Offline | 175 ms | — | |
| Offline | 176 ms | — | |
| Offline | 177 ms | — | |
| Offline | 172 ms | — | |
| Offline | 171 ms | — | |
| Offline | 175 ms | — | |
| Offline | 175 ms | — | |
| Offline | 177 ms | — | |
| Offline | 177 ms | — | |
| Offline | 180 ms | — | |
| Online | 167 ms | 0 | |
| Online | 176 ms | 0 | |
| Online | 175 ms | 0 | |
| Online | 178 ms | 0 | |
| Online | 168 ms | 0 | |
| Online | 178 ms | 0 | |
| Online | 176 ms | 0 | |
| Online | 169 ms | 0 | |
| Online | 180 ms | 0 | |
| Online | 175 ms | 0 | |
| Online | 173 ms | 0 | |
| Online | 166 ms | 0 | |
| Online | 174 ms | 0 | |
| Online | 169 ms | 0 | |
| Online | 173 ms | 0 | |
| Online | 171 ms | 0 |

1/125
Last checked 1 m ago
Wiped 2 d ago
Procedural Map
Rust 2x
0/100
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.