[EU] AshRust 2x Monthly Max 5 | QoL/Loot+ | No BPs [ 8 days online ]
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 9 s ago
88 / 100 players
Wiped 10 Days ago
2x Max 5 10 days live Avg ping 89.5 ms Avg jitter 3 ms Wipe cycle 0.2 ±0.2 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 81.16.176.138:22515
First seen 07.08.2026
Last wipe: (10 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 0 | |
| 0 | |
| 0.6 | |
| 0.4 | |
| 0 | |
| 0 | |
| — |
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | — | — | |
| Offline | 87 ms | — | |
| Offline | — | — | |
| Offline | — | — | |
| Offline | — | — | |
| Offline | — | — | |
| Online | — | 2 | |
| Offline | — | — | |
| Online | 93 ms | 3 | |
| Online | 87 ms | 6 | |
| Online | — | 75 | |
| Offline | 93 ms | — | |
| Online | 90 ms | 93 | |
| Online | 95 ms | 68 | |
| Offline | 97 ms | — | |
| Online | 87 ms | 4 | |
| Online | 87 ms | 7 | |
| Online | — | 13 | |
| Offline | — | — | |
| Online | 87 ms | 12 | |
| Online | — | 13 | |
| Online | — | 13 | |
| Online | 88 ms | 13 | |
| Online | — | 89 | |
| Online | 87 ms | 87 | |
| Online | 91 ms | 88 | |
| Online | — | 27 | |
| Online | 86 ms | 11 | |
| Online | 87 ms | 2 | |
| Online | — | 1 | |
| Online | — | 2 | |
| Online | — | 2 | |
| Offline | — | — | |
| Online | — | 4 | |
| Online | 86 ms | 9 | |
| Online | 87 ms | 9 | |
| Online | — | 90 | |
| Offline | 92 ms | — | |
| Online | 86 ms | 84 | |
| Online | 87 ms | 8 | |
| Online | — | 8 | |
| Offline | 88 ms | — | |
| Offline | 94 ms | — | |
| Offline | 88 ms | — | |
| Online | — | 2 | |
| Offline | 86 ms | — | |
| Offline | 87 ms | — | |
| Online | — | 11 | |
| Offline | — | — | |
| Online | 91 ms | 92 |
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.