Rust Data

rustdata.spaceservers213.230.109.15:28027.ipynb

Run all rust-data · live

‹ All servers

Online EA 213.230.109.15:28025 checked 10m ago

[Uz/Ru/Kz] #2 UzRust - Classic

biweekly wipes vanillamoddedoxide

Connect

srv = rust.server("213.230.109.15:28027")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,269 # top 68% · #472 in EA
last wipe 28d ago # biweekly schedule
next wipe 6d 22h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
0123421:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040021:0006:0015:0001:0010:0019:00

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
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 68% of all ranked servers, top 88% 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 22h. # The force wipe · high confidence

usual gap14.3 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

inatkind
06d 22hThu 5 Nov, 19:00 UTCFW force wipe
113d 22hThu 12 Nov, 18:57 UTCwipe
227d 22hThu 26 Nov, 18:57 UTCwipe
334d 22hThu 3 Dec, 19:00 UTCFW force wipe
441d 22hThu 10 Dec, 18:57 UTCwipe

The first 48 hours of its last wipes

Thu 1 OctThu 17 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:57 UTC FW28d ago 1 NaN running 0
1 Thu 17 Sep, 12:48 UTC42d ago 2 held half 14.3 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

3000 · seed 1974910435
Map of [Uz/Ru/Kz] #2 UzRust - Classic
map
Procedural Map
size
3000
seed
1974910435
Open on RustMaps

Server

srv.info()
address
213.230.109.15:28025
region
EA
max players
100
group limit
8, the default
wipe schedule
biweekly
last wipe
1 Oct 2026, 18:57 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
Добро пожаловать на UzRust! Классический Vanilla сервер без модов и изменений игрового процесса. Только настоящий Rust: выживание, PvP, рейды и борьба за ресурсы. • Vanilla • Вайп раз в месяц • Без вмешательства в баланс игры • Уважение к другим игрокам обязательно • Донат присутствует, но без нарушения атмосферы классического Rust Нарушители правил и читеры получают наказание. Связь по TG: t.me/@kaloel t.me/@ashovkatov

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 14 on average0/100
1瞌睡熊『5倍10废|10.30|萌新首选|无权限』EA · groups of 8+ · biweekly · 4 on average1/100
2[JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 2 on average0/50
3[JPN] Apple Server | PvP | Vanilla | 2WeeklyEA · groups of 8+ · biweekly · 2 on average1/50
4cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 2 on average1/50
5Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 76 on average201/250

Quick answers

From the figures on this page.

Population data

What position does [Uz/Ru/Kz] #2 UzRust - Classic take in the server rankings?

Ranked #15,269 on seven-day player hours, [Uz/Ru/Kz] #2 UzRust - Classic is #472 in Asia and in the top 68% of all ranked servers.

How many players does [Uz/Ru/Kz] #2 UzRust - Classic hold at once?

[Uz/Ru/Kz] #2 UzRust - Classic reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players.

About the server

How well does [Uz/Ru/Kz] #2 UzRust - Classic perform?

Server fps over the last 48 hours averages 188; the floor is 164. The entity count peaked at 45,123, covering buildings, deployables and the rest of the world. Memory peaked at 6,214 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does [Uz/Ru/Kz] #2 UzRust - Classic run?

The build is Rust network protocol 2634 and build 167781 on Windows, run by [Uz/Ru/Kz] #2 UzRust - Classic. Steam updates your game for you, but the protocol must match to join.

How reliable is [Uz/Ru/Kz] #2 UzRust - Classic, and is it online now?

Online is the state at the latest refresh for [Uz/Ru/Kz] #2 UzRust - Classic. Count back 7 days 17 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is [Uz/Ru/Kz] #2 UzRust - Classic hosted?

The EA tag is what [Uz/Ru/Kz] #2 UzRust - Classic uses to list itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 213.230.109.15:28025.

Rules, settings, map

Which settings and rules does [Uz/Ru/Kz] #2 UzRust - Classic run?

The name [Uz/Ru/Kz] #2 UzRust - Classic carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and 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 is running: Valve's anti-cheat is on.

Which map has [Uz/Ru/Kz] #2 UzRust - Classic selected?

The game generates the map on [Uz/Ru/Kz] #2 UzRust - Classic: procedural, size 3,000, seed 1974910435. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

On what schedule does [Uz/Ru/Kz] #2 UzRust - Classic wipe?

The prediction follows the tag, because [Uz/Ru/Kz] #2 UzRust - Classic's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 28 days 1 hours ago. The tags list a two-weekly wipe cycle.

On [Uz/Ru/Kz] #2 UzRust - Classic, what happens on wipe day?

The average peak over recent wipes is 2 players. 3 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags, lists

Where does [Uz/Ru/Kz] #2 UzRust - Classic appear among Rust Data lists and filters?

The Rust Data lists that [Uz/Ru/Kz] #2 UzRust - Classic fits are: Modded Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Which meanings do the tags on [Uz/Ru/Kz] #2 UzRust - Classic hold?

Read by the game's server browser, the tags [Uz/Ru/Kz] #2 UzRust - Classic publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; EA (East Asia): East Asia is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to [Uz/Ru/Kz] #2 UzRust - Classic?

Enter client.connect 213.230.109.15:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://uzrust.uz is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2634,^b,^v,EA,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

Region

EA
East Asia East Asia is its listing in the server browser.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 100,165 players 11,854 servers online