Name of Server as Shown on the Client Server List
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 2 m ago
0 / 10 players
Procedural Map
14 days live Avg ping 172.7 ms Avg jitter 9.6 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 175.118.147.95:28015
First seen 19.09.2026
Last wipe: (2 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| — |
Player count history
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 Sep 21 · 13:51 UTC Median daily peak 0 (median of daily peaks, not average population)
Observed daily peak
11 full · 0 partial · 4 offline · 16 no data
Population persistence across recent wipes
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.
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | 175 ms | — | |
| Offline | 163 ms | — | |
| Offline | 169 ms | — | |
| Offline | 174 ms | — | |
| Offline | 170 ms | — | |
| Offline | 162 ms | — | |
| Offline | 174 ms | — | |
| Offline | 172 ms | — | |
| Offline | 196 ms | — | |
| Offline | 186 ms | — | |
| Offline | 175 ms | — | |
| Offline | 172 ms | — | |
| Offline | 162 ms | — | |
| Offline | 173 ms | — | |
| Offline | 171 ms | — | |
| Offline | 172 ms | — | |
| Offline | 207 ms | — | |
| Offline | 161 ms | — | |
| Offline | 215 ms | — | |
| Offline | 193 ms | — | |
| Offline | 190 ms | — | |
| Offline | 171 ms | — | |
| Offline | 174 ms | — | |
| Offline | 176 ms | — | |
| Offline | 175 ms | — | |
| Offline | 169 ms | — | |
| Offline | 174 ms | — | |
| Offline | 175 ms | — | |
| Offline | 172 ms | — | |
| Offline | 176 ms | — | |
| Offline | 175 ms | — | |
| Offline | 175 ms | — | |
| Offline | 164 ms | — | |
| Offline | 162 ms | — | |
| Offline | 161 ms | — | |
| Offline | 175 ms | — | |
| Offline | 161 ms | — | |
| Offline | 160 ms | — | |
| Offline | 163 ms | — | |
| Offline | 175 ms | — | |
| Offline | 170 ms | — | |
| Offline | 169 ms | — | |
| Offline | 162 ms | — | |
| Offline | 162 ms | — | |
| Offline | 172 ms | — | |
| Offline | 172 ms | — | |
| Offline | 161 ms | — | |
| Offline | 176 ms | — | |
| Offline | 162 ms | — | |
| Offline | 162 ms | — |
Other servers in South Korea (low ping)
[NEW] 클라이서버 5x
Asia
| 자체 스킬트리 | 초보환영
5/30
Last checked 1 m ago
Wiped 2 d ago
5x Gather3 avg wipe peak
Vanilla
Vanilla
Procedural Map
Frequently asked questions
What does "wipe" mean in Rust?
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.
What does "force wipe" mean?
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.
How do I know when this server wipes?
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.
How do I connect to this server?
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.