1/200
Last checked 1 s ago
Wiped 2 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
225 ms · Chicago
Last checked 2 m ago
26 / 200 players
Procedural Map
24 days live Avg ping 223.8 ms Avg jitter 13.1 ms Wipe cycle 4.3 ±2 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 160.202.248.48:28015
First seen 09.09.2026
Last wipe: (2 d ago)
| Wiped | Days since previous |
|---|---|
| 1.5 | |
| 4.1 | |
| 7.1 | |
| 2.9 | |
| 6.2 | |
| — |
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 28 Sep 26 · 02:24 UTC Median daily peak 26 (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 |
|---|---|---|---|
| Online | 225 ms | 26 | |
| Online | — | 26 | |
| Online | 222 ms | 26 | |
| Online | 232 ms | 26 | |
| Online | 231 ms | 25 | |
| Online | 233 ms | 25 | |
| Online | 218 ms | 25 | |
| Online | 216 ms | 25 | |
| Online | 224 ms | 25 | |
| Online | 209 ms | 25 | |
| Offline | 243 ms | — | |
| Online | 226 ms | 23 | |
| Online | 222 ms | 22 | |
| Online | 228 ms | 22 | |
| Online | 243 ms | 22 | |
| Online | 240 ms | 21 | |
| Online | 215 ms | 21 | |
| Online | 217 ms | 21 | |
| Online | 220 ms | 21 | |
| Offline | — | — | |
| Online | 229 ms | 21 | |
| Online | 230 ms | 21 | |
| Online | 244 ms | 21 | |
| Online | 223 ms | 21 | |
| Offline | 220 ms | — | |
| Online | 242 ms | 21 | |
| Online | 231 ms | 21 | |
| Online | 223 ms | 21 | |
| Online | 207 ms | 21 | |
| Online | 219 ms | 21 | |
| Online | 223 ms | 21 | |
| Offline | 233 ms | — | |
| Online | 212 ms | 22 | |
| Offline | 239 ms | — | |
| Online | 218 ms | 21 | |
| Online | 221 ms | 25 | |
| Online | 229 ms | 26 | |
| Online | 218 ms | 25 | |
| Online | 208 ms | 25 | |
| Online | 251 ms | 25 | |
| Online | 218 ms | 25 | |
| Online | 207 ms | 24 | |
| Online | 228 ms | 25 | |
| Online | 268 ms | 24 | |
| Online | — | 24 | |
| Online | — | 24 | |
| Offline | 229 ms | — | |
| Online | — | 24 | |
| Offline | 208 ms | — | |
| Online | 209 ms | 24 |
1/200
Last checked 1 s ago
Wiped 2 d ago
Procedural Map

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