KontiRust | PVE
Russia
x1.5 | Events | Monthly
2/50
Last checked 2 s ago
Wiped 22 h ago
3% elapsed97% left
Next wipe in 29 days
1.5x Gather5 avg wipe peak
Vanilla
Vanilla
Procedural Map
HYDRA MAIN | X1.5 | NOLIMIT
Server admin? Sign in with Steam to claim this server.
127 ms · Chicago
Last checked 8 m ago
0 / 100 players
Procedural Map
1.5x 53 days live Avg ping 135.3 ms Avg jitter 27.5 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 212.22.93.190:28024
First seen 11.08.2026
Last wipe: (29 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| — |
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 0 Oct 1 · 19:45 UTC Median daily peak 0 (median of daily peaks, not average population)
Observed daily peak
3 full · 0 partial · 5 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.
Not enough wipe history yet to compare cycles — this fills in as more wipes complete.
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Offline | 121 ms | — | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 253 ms | 0 | |
| Online | 242 ms | 0 | |
| Online | 226 ms | 0 | |
| Online | 148 ms | 0 | |
| Online | 135 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 133 ms | 0 | |
| Online | 134 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 172 ms | 0 | |
| Online | 172 ms | 0 | |
| Online | 172 ms | 0 | |
| Online | 172 ms | 0 | |
| Online | 172 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 133 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 127 ms | 0 | |
| Online | 133 ms | 0 | |
| Online | 127 ms | 0 |
Other 1.5x servers in Russia (low ping)
TRUST | PVE
Russia
x1.5 | Events | Monthly
1/50
Last checked 44 s ago
Wiped 1 d ago
6% elapsed94% left
Next wipe in 28 days
1.5x Gather1 avg wipe peakVanilla
VanillaProcedural Map
MoonEclipse 1.5X EU
Russia
NOLIM 02 10
0/100
Last checked 9 m ago
Wiped 1 d ago
1.5x Gather14 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.