US LushPvE Monthly
Europe
2x | Skills | Events | Npc Raids | Quests
2/50
Last checked 4 m ago
Wiped 1 d ago
5% elapsed95% left
Next wipe in 28 days
2x Gather6 avg wipe peak
Vanilla
Vanilla
Lush Custom PvE Maps
[UA] PVE Server
Server admin? Sign in with Steam to claim this server.
90 ms · Chicago
Jitter 0.7 ms
Last checked 5 m ago
0 / 5 players
Procedural Map
56 days live Avg ping 91.6 ms Avg jitter 1.1 ms Wipe cycle 14 ±12.9 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 198.244.225.27:25638
First seen 07.08.2026
Last wipe: (1 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 26.9 | |
| 1.1 | |
| — |
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 2 Sep 15 · 20:15 UTC Median daily peak 0 (median of daily peaks, not average population)
Observed daily peak
31 full · 0 partial · 0 offline · 0 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
- Sep 3
Server info
No PvP
No raiding.
Do not steal
Respect other players
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 90 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 90 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 91 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 93 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 92 ms | 0 | |
| Online | 91 ms | 0 |
Other servers in United Kingdom (low ping)
US Velt.gg 2x
Europe
Monthly Trio Premium |50% Upkeep|No BP Wipes|x2
1/200
Last checked 4 m ago
Wiped 1 d ago
5% elapsed95% left
Next wipe in 28 days
US Vex.gg 2x
Europe
Monthly Duo/Trio/Quad Premium|50% Upkeep|Max 4|x2
1/200
Last checked 36 s ago
Wiped 1 d ago
5% elapsed95% left
Next wipe in 28 days
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.