

| FULLWIPE 15/11 15.11 11/15
2/215
Last checked 1 m ago
Wiped 1 d ago
Server admin? Sign in with Steam to claim this server.
No reading yet from Chicago
Server admin? We haven't been able to get a ping reading for your server from Chicago yet, which can keep it from ranking well for players browsing that region. This usually means a firewall or DDoS-protection rule is blocking the brief, unsolicited connection check we send to your game port — the same kind of lightweight check the game client itself uses, separate from your server's normal browser-listing info. Allowing that check through on your game port should let us start measuring and showing an accurate ping for your server there.
Last checked 6 m ago
0 / 40 players
Procedural Map
2 days live Avg ping 252.4 ms Avg jitter 6.8 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 13.207.204.147:28015
First seen 14.11.2026
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 1 Nov 15 · 03:31 UTC Median daily peak 0 (median of daily peaks, not average population)
Observed daily peak
4 full · 0 partial · 0 offline · 27 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.
Not enough wipe history yet to compare cycles — this fills in as more wipes complete.
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | 254 ms | — | |
| Offline | 250 ms | — | |
| Offline | 261 ms | — | |
| Offline | 252 ms | — | |
| Offline | 246 ms | — | |
| Offline | 253 ms | — | |
| Offline | 249 ms | — | |
| Offline | 279 ms | — | |
| Offline | 249 ms | — | |
| Offline | 245 ms | — | |
| Offline | 251 ms | — | |
| Offline | 252 ms | — | |
| Offline | 251 ms | — | |
| Offline | 259 ms | — | |
| Offline | 250 ms | — | |
| Offline | 260 ms | — | |
| Offline | 250 ms | — | |
| Offline | 247 ms | — | |
| Offline | 256 ms | — | |
| Offline | 247 ms | — | |
| Offline | 246 ms | — | |
| Offline | 249 ms | — | |
| Offline | 259 ms | — | |
| Offline | 249 ms | — | |
| Offline | 242 ms | — | |
| Offline | 252 ms | — | |
| Offline | 248 ms | — | |
| Offline | 258 ms | — | |
| Offline | 253 ms | — | |
| Offline | 254 ms | — |


| FULLWIPE 15/11 15.11 11/15
2/215
Last checked 1 m ago
Wiped 1 d ago


#3 | FULLWIPE 16/11 16.11 11/16
1/215
Last checked 1 m ago
Wiped 1 d ago


Weekly | FULLWIPE 11/11 11.11 11/11
0/215
Last checked 47 s ago
Wiped 5 d ago
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.