INDUSTRIAL PVE BiWeekly
Russia
X2 [ BOSS / SKILL / NEW MODS ]
12/250
Last checked 1 m ago
Wiped 2 d ago
20% elapsed80% left
Next wipe in 11 days
2x Gather20 avg wipe peak
Vanilla
Vanilla
Custom Map
MOG RUST | x2 | SEMI | WIPE THU
Server admin? Sign in with Steam to claim this server.
140 ms · Chicago
Jitter 26.9 ms
Last checked 6 m ago
0 / 200 players
Custom Map
2x 12 days live Avg ping 138.4 ms Avg jitter 6.1 ms Wipe cycle 3.3 ±2.1 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 79.137.192.240:28015
First seen 22.09.2026
Last wipe: (2 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 6.1 | |
| 1.1 | |
| 2.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 3 Sep 27 · 09:33 UTC Median daily peak 0 (median of daily peaks, not average population)
Observed daily peak
8 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 25
- Sep 24
- Sep 22
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 140 ms | 0 | |
| Online | 178 ms | 0 | |
| Online | 134 ms | 0 | |
| Online | 129 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 143 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 131 ms | 0 | |
| Online | 136 ms | 0 | |
| Online | 130 ms | 0 | |
| Offline | — | — | |
| Online | 138 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 161 ms | 0 | |
| Online | 152 ms | 0 | |
| Online | 136 ms | 0 | |
| Online | 135 ms | 0 | |
| Online | 128 ms | 0 | |
| Online | 129 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 129 ms | 0 | |
| Online | 133 ms | 0 | |
| Online | 130 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 135 ms | 0 | |
| Online | 130 ms | 0 | |
| Online | 129 ms | 0 | |
| Online | 135 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 142 ms | 0 | |
| Online | 135 ms | 0 | |
| Online | 149 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 135 ms | 0 | |
| Online | 133 ms | 0 | |
| Online | 137 ms | 0 | |
| Online | 136 ms | 0 | |
| Online | 136 ms | 0 | |
| Online | 136 ms | 0 | |
| Online | 137 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 138 ms | 0 | |
| Online | 144 ms | 0 | |
| Online | 144 ms | 0 |
Other 2x servers in Russia (low ping)
#2 PANDORUM MAX3
Russia
| X2 | SOLO/DUO/TRIO
0/100
Last checked 35 s ago
Wiped 2 d ago
2x GatherMax 32 avg wipe peakVanilla
VanillaProcedural Map
AQRUX RUST BLACK
Russia
X2 | TP | KIT | CLANS | 02.10
24/200
Last checked 3 m ago
Wiped 2 d ago
2x Gather18 avg wipe peakVanilla
VanillaFPS+ | ВАЙП 2Д НАЗАД
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.