
[US] Lagoon 1.5x
North America
| Solo/Duo/Trio | 10/1
3/100
Last checked 3 m ago
Wiped 2 d ago
Custom Map
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 53 s ago
0 / 69 players
Procedural Map
1.5x 45 days live Avg ping 35.6 ms Avg jitter 9 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 108.238.244.110:28015
First seen 19.08.2026
Last wipe: (2 d ago)
| Wiped | Days since previous |
|---|---|
| — |
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 4 Sep 28 · 22:04 UTC Median daily peak 2 (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.
Not enough wipe history yet to compare cycles — this fills in as more wipes complete.
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | 28 ms | — | |
| Offline | 42 ms | — | |
| Offline | 43 ms | — | |
| Offline | 28 ms | — | |
| Offline | 28 ms | — | |
| Offline | 42 ms | — | |
| Offline | 27 ms | — | |
| Offline | 29 ms | — | |
| Offline | 43 ms | — | |
| Offline | 28 ms | — | |
| Offline | 29 ms | — | |
| Offline | 29 ms | — | |
| Offline | 28 ms | — | |
| Offline | 41 ms | — | |
| Offline | 29 ms | — | |
| Offline | 42 ms | — | |
| Offline | 43 ms | — | |
| Offline | 28 ms | — | |
| Offline | 43 ms | — | |
| Offline | 29 ms | — | |
| Offline | 43 ms | — | |
| Offline | 41 ms | — | |
| Offline | 42 ms | — | |
| Offline | 28 ms | — | |
| Offline | 27 ms | — | |
| Offline | 28 ms | — | |
| Offline | 43 ms | — | |
| Offline | 29 ms | — | |
| Offline | 43 ms | — | |
| Offline | 42 ms | — | |
| Offline | 41 ms | — | |
| Offline | 43 ms | — | |
| Offline | 30 ms | — | |
| Offline | 27 ms | — | |
| Offline | 42 ms | — | |
| Offline | 41 ms | — | |
| Offline | 28 ms | — | |
| Offline | 28 ms | — | |
| Offline | 29 ms | — | |
| Offline | 42 ms | — | |
| Offline | 28 ms | — | |
| Offline | 43 ms | — | |
| Offline | 27 ms | — | |
| Offline | 41 ms | — | |
| Offline | 43 ms | — | |
| Offline | 28 ms | — | |
| Offline | 43 ms | — | |
| Offline | 29 ms | — | |
| Offline | 42 ms | — | |
| Offline | 42 ms | — |

North America
| Solo/Duo/Trio | 10/1
3/100
Last checked 3 m ago
Wiped 2 d ago
Custom Map


North America
Main 1.5x | Vanilla
3/150
Last checked 51 s ago
Wiped 2 d ago
Custom Map


North America
Solo/Duo/Trio/Quad | 1.5x | 2500 Map Rai
0/50
Last checked 5 m ago
Wiped 2 d ago
Custom 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.