『柠萌PVE』死亡不掉 | 无限成长 | 高手进阶
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 1 m ago
3 / 200 players
Custom Map
5 days live Avg ping 207.2 ms Avg jitter 11.9 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 125.38.165.30:21015
First seen 27.09.2026
Last wipe: (1 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 27.7 | |
| — |
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 15 Oct 2 · 11:47 UTC Median daily peak 9 (median of daily peaks, not average population)
Observed daily peak
7 full · 0 partial · 0 offline · 24 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.
- Oct 1
- Sep 4
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | 210 ms | — | |
| Offline | 203 ms | — | |
| Online | — | 8 | |
| Online | 205 ms | 10 | |
| Offline | 199 ms | — | |
| Online | 192 ms | 3 | |
| Online | 227 ms | 1 | |
| Offline | 195 ms | — | |
| Offline | — | — | |
| Offline | — | — | |
| Offline | 209 ms | — | |
| Offline | 211 ms | — | |
| Offline | — | — | |
| Offline | 216 ms | — | |
| Offline | 217 ms | — | |
| Offline | 194 ms | — | |
| Online | 195 ms | 2 | |
| Online | 193 ms | 0 | |
| Online | 193 ms | 0 | |
| Online | — | 0 | |
| Online | 205 ms | 3 | |
| Offline | 239 ms | — | |
| Online | 212 ms | 4 | |
| Online | 195 ms | 5 | |
| Online | 201 ms | 8 | |
| Offline | 210 ms | — | |
| Online | 194 ms | 3 | |
| Online | 199 ms | 0 | |
| Online | 206 ms | 4 | |
| Online | 207 ms | 4 | |
| Online | 218 ms | 4 | |
| Online | 222 ms | 6 | |
| Online | 214 ms | 6 | |
| Online | 195 ms | 4 | |
| Online | 214 ms | 5 | |
| Online | 219 ms | 7 | |
| Online | 194 ms | 5 | |
| Online | 193 ms | 1 | |
| Online | 202 ms | 3 | |
| Online | 195 ms | 4 | |
| Online | 196 ms | 7 | |
| Online | 209 ms | 7 | |
| Online | 234 ms | 6 | |
| Online | 196 ms | 4 | |
| Online | 227 ms | 2 | |
| Online | 201 ms | 2 | |
| Online | 220 ms | 2 | |
| Online | 193 ms | 1 | |
| Online | 204 ms | 3 | |
| Online | 219 ms | 3 |
Other servers in China (low ping)
0/200
Last checked 5 m ago
Wiped 1 d ago
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.