B2 FAST [DUO
Russia
| X3 | TP | KITS | FPS+] 03.10 #bear
10/200
Last checked 21 s ago
Wiped 6 h ago
3x GatherMax 215 avg wipe peak
Vanilla
Vanilla
Procedural Map
![ZRust #7 [ x3 | Kits | TP | NO Clans ] banner](https://i.ibb.co/YkBgMFH/6605578-4.jpg)
ZRust #7 [ x3 | Kits | TP | NO Clans ]
Server admin? Sign in with Steam to claim this server.
143 ms · Chicago
Jitter 2.1 ms
Last checked 40 s ago
0 / 100 players
Procedural Map
3x 57 days live Avg ping 155 ms Avg jitter 15.6 ms Wipe halving: 2 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 5.166.240.61:28019
First seen 07.08.2026
Last wipe: (1 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 28 | |
| — |
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 18 · 17:05 UTC Median daily peak 1 (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 3
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 143 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 1 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 1 | |
| Online | 140 ms | 2 | |
| Online | 141 ms | 2 | |
| Online | 144 ms | 1 | |
| Online | 142 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 156 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 159 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 141 ms | 0 | |
| Online | 157 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 144 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 162 ms | 0 | |
| Online | 142 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 158 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 161 ms | 0 | |
| Online | 146 ms | 1 | |
| Online | 140 ms | 0 | |
| Online | 140 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 147 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 139 ms | 0 | |
| Online | 163 ms | 0 | |
| Online | 161 ms | 0 |
Other 3x servers in Russia (low ping)
.png){kind=logo}
#4 WARZONE X3
Russia
[MAX2|DUO|TP|KIT|EVENT|COPTER]
7/100
Last checked 4 m ago
Wiped 13 h ago
3x GatherMax 26 avg wipe peak
Modded
ModdedCustom Map
DOOM RUST X3
Russia
3/200
Last checked 4 m ago
Wiped 1 d ago
3x Gather5 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.