[EU/CZ/SK] ZeddiHub |
Europe
PVP | 3x [Solo/Duo/Trio]
0/30
Last checked 5 m ago
Wiped 1 d ago
6% elapsed94% left
Next wipe in 28 days
3x GatherMax 30 avg wipe peak
Vanilla
Vanilla
Procedural Map
![[EU/CZ] RustyMind | 3x - Wiped 2/10 1 day ago banner](https://r2.fivemanage.com/HcQGfeCXJQxQon3lN5AoR/rustymind_512x256.png)
[EU/CZ] RustyMind | 3x - Wiped 2/10 1 day ago
Server admin? Sign in with Steam to claim this server.
106 ms · Chicago
Jitter 0 ms
Last checked 59 s ago
1 / 50 players
Procedural Map
3x 57 days live Avg ping 108.3 ms Avg jitter 6.2 ms Wipe cycle 14 ±3.5 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 185.180.2.12:28820
First seen 07.08.2026
Last wipe: (1 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 17.5 | |
| 10.5 | |
| — |
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 4 Aug 18 Median daily peak 1 (median of daily peaks, not average population)
Observed daily peak
58 full · 0 partial · 0 offline · 33 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 14
- Sep 3
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 106 ms | 1 | |
| Online | 106 ms | 1 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Offline | 106 ms | — | |
| Online | 106 ms | 1 | |
| Online | 106 ms | 0 | |
| Online | 113 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Offline | 112 ms | — | |
| Online | 112 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 114 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 107 ms | 0 | |
| Online | 112 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 | |
| Online | 106 ms | 0 |
Other 3x servers in Czechia (low ping)
LAJKTO EU 3X
Europe
| No BPs | Quad | Monthly
0/64
Last checked 2 m ago
Wiped 1 d ago
6% elapsed94% left
Next wipe in 28 days
3x GatherMax 40 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.