
[TR] Dirilis 3X
Middle East
- Solo/Duo/Trio/Quad|Max 5 Yeni Baslayan
2/300
Last checked 2 m ago
Wiped 39 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
No reading yet from Chicago
Server admin? We haven't been able to get a ping reading for your server from Chicago yet, which can keep it from ranking well for players browsing that region. This usually means a firewall or DDoS-protection rule is blocking the brief, unsolicited connection check we send to your game port — the same kind of lightweight check the game client itself uses, separate from your server's normal browser-listing info. Allowing that check through on your game port should let us start measuring and showing an accurate ping for your server there.
Last checked 2 m ago
0 / 100 players
Procedural Map
10 days live Avg ping 147.8 ms Avg jitter 5 ms
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 37.221.76.139:28107
First seen 22.09.2026
Last wipe: (1 d ago)
| Wiped | Days since previous |
|---|---|
| — |
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 1 Sep 22 · 12:46 UTC Median daily peak 0 (median of daily peaks, not average population)
Observed daily peak
12 full · 0 partial · 0 offline · 79 no data
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.
| Checked | Status | Ping | Players |
|---|---|---|---|
| Offline | — | — | |
| Offline | 152 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 151 ms | — | |
| Offline | 147 ms | — | |
| Offline | 145 ms | — | |
| Offline | 152 ms | — | |
| Offline | 151 ms | — | |
| Offline | 151 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 151 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 153 ms | — | |
| Offline | 147 ms | — | |
| Offline | 145 ms | — | |
| Offline | 153 ms | — | |
| Offline | 151 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | — | — | |
| Offline | 145 ms | — | |
| Offline | — | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 146 ms | — | |
| Offline | 160 ms | — | |
| Offline | 164 ms | — | |
| Offline | 165 ms | — | |
| Offline | 165 ms | — | |
| Offline | 151 ms | — | |
| Offline | 151 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 151 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 151 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — | |
| Offline | 145 ms | — |

Middle East
- Solo/Duo/Trio/Quad|Max 5 Yeni Baslayan
2/300
Last checked 2 m ago
Wiped 39 d ago
Procedural Map

Middle East
Max 6 | Kits | Bots | Loot X3 | Raid Bases
0/123
Last checked 4 m ago
Wiped 15 d ago
Procedural Map

Middle East
Solo Duo | Yeni başlayanlar için
23/200
Last checked 2 m ago
Wiped 1 d ago
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.
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.
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.
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.