[TR] Dirilis 3X - Solo/Duo/Trio/Quad|Max 5 Yeni Baslayan
Server admin? Sign in with Steam to claim this server.
147 ms · Chicago
Jitter 7.5 ms
Last checked 4 s ago
9 / 300 players
Dirilis Rust FPS+ | 3 Days Ago
3x Max 5 101 days live Avg ping 140.3 ms Avg jitter 5.4 ms Wipe cycle 2 ±2.5 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 46.203.182.220:10003
First seen 07.08.2026
Last wipe: (84 d ago)
Wipe history
| Wiped | Days since previous |
|---|---|
| 7 | |
| 1.7 | |
| 1.2 | |
| 4.1 | |
| 7 | |
| 2.9 | |
| 4.1 | |
| 2.9 | |
| 4.1 | |
| 2.8 | |
| 4.2 | |
| 1.7 | |
| 1.2 | |
| 4.1 | |
| 2.9 | |
| 4.1 | |
| 2.9 | |
| 4.1 | |
| 2.9 | |
| 5.8 | |
| 10 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| — |
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 63 Nov 7 Median daily peak 14 (median of daily peaks, not average population)
Observed daily peak
81 full · 0 partial · 0 offline · 10 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.
Server info
---SOLO DUO TRİO QUAD MAX 5---
Wipe: Çarşamba 17:00 - Cumartesi 14:00
Discord: discord.gg/DIRILISRust
VIP olmak icin Discord'a katilin!
--- Sunucu Özellikleri ---
- 3x Loot (Dizel 3x Stack 3x)
- 3x Craft Hizi
- Skinbox /skinbox
- Hizli Eritme ve Geri Donusturme
- Aktif Adminler & Lagsiz Oyun
- Essiz Kitler /kit
--- Kurallar ---
Hile / Bug kullanimi yasaktir.
Son 30 gun icinde Rust yasaginiz olmamalidir.
Hilecilerle oynamak yasaktir.
Detaylar icin: F1 Konsolu
Ping history from Chicago
Jitter history
Recent history from Chicago
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 147 ms | 6 | |
| Online | 139 ms | 5 | |
| Online | 132 ms | 2 | |
| Online | 136 ms | 1 | |
| Online | 135 ms | 3 | |
| Online | 147 ms | 10 | |
| Online | 136 ms | 19 | |
| Online | 138 ms | 29 | |
| Online | 144 ms | 22 | |
| Online | 139 ms | 15 | |
| Online | 140 ms | 14 | |
| Online | 138 ms | 7 | |
| Online | 140 ms | 10 | |
| Online | 141 ms | 6 | |
| Online | 141 ms | 7 | |
| Online | 151 ms | 15 | |
| Online | 136 ms | 23 | |
| Online | 137 ms | 29 | |
| Online | 140 ms | 30 | |
| Online | 139 ms | 32 | |
| Online | 145 ms | 23 | |
| Online | 142 ms | 21 | |
| Online | 134 ms | 12 | |
| Online | 140 ms | 7 | |
| Online | 139 ms | 6 | |
| Online | 142 ms | 14 | |
| Online | 141 ms | 35 | |
| Online | 141 ms | 42 | |
| Online | 140 ms | 46 |
Other 3x servers in Turkey (low ping)


[TR/EU] TURK RUST
Middle East
3X - MAX 5 | Yeni Başlayan FULL WIPE !!
1/200
Last checked 2 m ago
Wiped 2 d ago

[TR] HOUSEOFPASHAS 3X
Middle East
| Max 6 | Yeni Başlayan | Aylık Wipe
0/100
Last checked 2 m ago
Wiped 3 d ago
Procedural 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.