Online EA 213.230.109.15:28015 checked 8m ago
[Uz/Ru/Kz] #1 UzRust - Modded
Connect
srv = rust.server("213.230.109.15:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 30% of all ranked servers, top 72% in EA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 12h | Thu 12 Nov, 11:24 UTC | wipe |
| 2 | 20d 12h | Thu 19 Nov, 11:24 UTC | wipe |
| 3 | 27d 12h | Thu 26 Nov, 11:24 UTC | wipe |
| 4 | 34d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 41d 12h | Thu 10 Dec, 11:24 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 20 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 11:24 UTC11h ago | NaN | NaN | running | 0 |
| 1 | Thu 8 Oct, 13:18 UTC21d ago | 5 | NaN | NaN | 0 |
| 2 | Thu 1 Oct, 18:30 UTC FW28d ago | 8 | halved by day 4 | 6.8 days | 2 |
| 3 | Thu 24 Sep, 13:15 UTC35d ago | 7 | held half | 7.2 days | 1 |
| 4 | Thu 17 Sep, 13:44 UTC42d ago | 7 | halved by day 4 | 7 days | 0 |
# Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())
Map
2000 · seed 201110278
- map
- Procedural Map
- size
- 2000
- seed
- 201110278
Server
srv.info()- address
- 213.230.109.15:28015
- region
- EA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 29 Oct 2026, 14:03 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | QS『芬达』100000倍/10.30/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 25 on average | 28/100 |
| 1 | 【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐 | EA · groups of 8+ · weekly · 22 on average | 0/200 |
| 2 | 〈红牛〉 五倍6人服/10.28号18:00新开 |新手入门| | EA · groups of 30+ · weekly · 3 on average | 2/200 |
| 3 | 【独来独往】10.27新档|3倍|独狼Solo|秒造|拾取 | EA · groups of 8+ · weekly · 2 on average | 2/200 |
| 4 | Rustoria.co - SEA Main | EA · groups of 16+ · weekly · 181 on average | 155/200 |
| 5 | Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com | EA · groups of 16+ · weekly · 119 on average | 2/550 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does [Uz/Ru/Kz] #1 UzRust - Modded rank?
Player hours over the last seven days: #6,608 for [Uz/Ru/Kz] #1 UzRust - Modded, #388 in Asia, within the top 30% of the ranked set.
What population does [Uz/Ru/Kz] #1 UzRust - Modded carry?
[Uz/Ru/Kz] #1 UzRust - Modded reports 1 players at this refresh, with 100 slots configured. Over the last seven days it averaged 2 players and peaked at 4. Peak hour in the last 48 hours: 17:00 UTC, mean 3 players.
About the server
How smoothly does [Uz/Ru/Kz] #1 UzRust - Modded run?
The 48-hour average is 231 server fps, with a low of 219. Buildings, deployables and all else in the world took the count as high as 69,353 entities. A high of 2,317 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is [Uz/Ru/Kz] #1 UzRust - Modded on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by [Uz/Ru/Kz] #1 UzRust - Modded. Steam updates your game for you, but the protocol must match to join.
How reliable is [Uz/Ru/Kz] #1 UzRust - Modded, and is it up?
[Uz/Ru/Kz] #1 UzRust - Modded reports itself online at the current refresh. Count back 6 hours from its reported uptime to get the last restart. 16 of 168 hours up over the last 7 full days, or 10%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is [Uz/Ru/Kz] #1 UzRust - Modded hosted?
In Asia, [Uz/Ru/Kz] #1 UzRust - Modded lists itself, using the EA tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 213.230.109.15:28015 is its address.
Rules, settings, map
Which settings and rules does [Uz/Ru/Kz] #1 UzRust - Modded run?
The name [Uz/Ru/Kz] #1 UzRust - Modded carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.
What is the map on [Uz/Ru/Kz] #1 UzRust - Modded?
The game generates the map on [Uz/Ru/Kz] #1 UzRust - Modded: procedural, size 2,000, seed 201110278. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does [Uz/Ru/Kz] #1 UzRust - Modded wipe, and how often?
The prediction follows the tag, because [Uz/Ru/Kz] #1 UzRust - Modded's wipes on record are too few to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 8 hours ago, and that is the one in play. A weekly wipe schedule is published in its tags.
On [Uz/Ru/Kz] #1 UzRust - Modded, what happens on wipe day?
The average peak over recent wipes is 7 players. Peak population on the latest wipe came 20 hours in. Half the peak or more was held to the next wipe in 25% of recent wipes. The drop under half arrived by day 4 in the other cases.
Tags and filters
Where does [Uz/Ru/Kz] #1 UzRust - Modded appear among Rust Data lists and filters?
On Rust Data, [Uz/Ru/Kz] #1 UzRust - Modded appears in these lists: Modded Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours.
How should you read the server tags on [Uz/Ru/Kz] #1 UzRust - Modded?
These tags are published by [Uz/Ru/Kz] #1 UzRust - Modded and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^w (Weekly): A wipe every week; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; EA (East Asia): In the server browser it sits under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join [Uz/Ru/Kz] #1 UzRust - Modded?
Enter client.connect 213.230.109.15:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://uzrust.uz/.
