DRIFT EU |
Europe
2X Solo/Duo | Naval PvP | Weekly | JUST WIPED
3/75
Last checked 3 m ago
Wiped 2 d ago
35% elapsed65% left
Next wipe in 4 days
2x GatherMax 28 avg wipe peak
Vanilla
Vanilla
Custom Map
RustVikings | Solo/Duo | 2X | FULLWIPE 02/10 14:00CEST
Server admin? Sign in with Steam to claim this server.
96 ms · Chicago
Jitter 2.9 ms
Last checked 1 m ago
0 / 200 players
Custom Map
2x Max 2 13 days live Avg ping 98.7 ms Avg jitter 2.4 ms Wipe halving: 3 days Wipe cycle 4 ±1.9 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 193.25.252.90:28076
First seen 19.09.2026
Last wipe: (3 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 1.3 | |
| 5 | |
| 5.6 | |
| — |
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 10 Sep 25 · 12:14 UTC Median daily peak 2 (median of daily peaks, not average population)
Observed daily peak
15 full · 0 partial · 0 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.
- Sep 30
- Sep 25
- Sep 19
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 96 ms | 1 | |
| Online | 96 ms | 0 | |
| Online | 101 ms | 1 | |
| Online | 101 ms | 0 | |
| Online | 100 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 2 | |
| Online | 101 ms | 3 | |
| Online | 101 ms | 1 | |
| Online | 101 ms | 3 | |
| Online | 96 ms | 1 | |
| Online | 96 ms | 1 | |
| Online | 96 ms | 1 | |
| Online | 96 ms | 1 | |
| Online | 100 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 101 ms | 0 | |
| Offline | 101 ms | — | |
| Online | 96 ms | 2 | |
| Online | 101 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 101 ms | 1 | |
| Online | 96 ms | 0 | |
| Online | — | 0 | |
| Online | 101 ms | 0 | |
| Online | 96 ms | 1 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 100 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 96 ms | 1 | |
| Online | 96 ms | 0 | |
| Online | 100 ms | 0 | |
| Online | 96 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 101 ms | 0 | |
| Online | 96 ms | 1 | |
| Online | 101 ms | 1 | |
| Online | 96 ms | 0 | |
| Online | 96 ms | 0 |
Other 2x servers in Netherlands (low ping)
EU 2x The
Europe
Raid Redemption PVE - Kits/CustomVehicles
6/30
Last checked 2 m ago
Wiped 1 d ago
2x Gather8 avg wipe peakVanilla
VanillaProcedural Map
Holy Rust |
Europe
x2 Main | WIPE 02/10
0/125
Last checked 55 s ago
Wiped 16 h ago
2x Gather1 avg wipe peakVanilla
VanillaProcedural 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.