Skip to the content
Dive report

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

Online EA 213.230.109.15:28025 checked 12m ago

biweekly wipes vanillamoddedoxide
Drop in
0/ 100 players now 0% full
07-day averagepeak 2
#5,365ranktop 24% · #377 in EA
16d agolast wipebiweekly schedule
11d 9hnext wipeThu 29 Oct, 18:57 UTC

Players

AveragePeak
00.511.5210:0019:0004:0014:0023:0008:00

Hourly average and peak, UTC.

Server performance

010020030040010:0019:0004:0014:0023:0008: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
RankRank in region
12k4k6k8k20 Sep26 Sep1 Oct7 Oct12 Oct18 Oct

Top 24% of all ranked servers, top 69% in EA. Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 18:57 UTC, in 11d 9h. Its biweekly schedule tag · low confidence

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

Coming wipes

  • 11d 9h
    Thu 29 Oct, 18:57 UTC
  • 18d 9h
    Thu 5 Nov, 19:00 UTC
    FW
  • 25d 9h
    Thu 12 Nov, 18:57 UTC
  • 39d 9h
    Thu 26 Nov, 18:57 UTC

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
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:57 UTC FW16d ago 1 – running 0
Thu 17 Sep, 12:48 UTC30d 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.

Neighbouring dive spots

Similar servers

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

From the figures on this page

Quick answers

Tags and search

Where does [Uz/Ru/Kz] #2 UzRust - Classic appear in Rust Going Deep lists and filters?

The Rust Going Deep lists that carry [Uz/Ru/Kz] #2 UzRust - Classic are: Modded Rust servers. Its entry appears under the filters 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.

What's the meaning of the tags on [Uz/Ru/Kz] #2 UzRust - Classic?

[Uz/Ru/Kz] #2 UzRust - Classic's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp100 (Max players): It holds 100 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): It's on build 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Facepunch's version, untouched: no rate changes, no kits, no extra rules; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; EA (East Asia): The server browser lists it under East Asia. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.

Server info

Is [Uz/Ru/Kz] #2 UzRust - Classic lag-free?

Average server fps for the last 48 hours was 202, and the lowest was 42. Buildings, deployables and all other world objects added up to as many as 45,491 entities. Memory use peaked at 2,148 MB. A climbing entity count together with low fps is what feels like lag to players.

Where can you find [Uz/Ru/Kz] #2 UzRust - Classic?

[Uz/Ru/Kz] #2 UzRust - Classic lists Asia as its location, with the EA tag. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 213.230.109.15:28025.

What's the uptime like for [Uz/Ru/Kz] #2 UzRust - Classic?

[Uz/Ru/Kz] #2 UzRust - Classic is up and reachable at the moment. The uptime it gives puts the last restart at roughly 7 hours ago. In the last full 7 days, 168 of 168 hours were online, 100% uptime. Rust Going Deep has had it on record since 13 September 2026.

What Rust version is [Uz/Ru/Kz] #2 UzRust - Classic on?

On Windows, [Uz/Ru/Kz] #2 UzRust - Classic runs Rust network protocol 2634 and build 167781. The protocol must match to join; Steam will update your game.

Wipe info

How often does [Uz/Ru/Kz] #2 UzRust - Classic wipe?

With too few wipes recorded for [Uz/Ru/Kz] #2 UzRust - Classic to confirm the schedule, the prediction goes by its tag. Expect the next wipe on Thursday 29 October at 18:57 UTC. This world has been running since 16 days 14 hours ago. Its tags list a wipe schedule for every two weeks.

What happens on wipe day at [Uz/Ru/Kz] #2 UzRust - Classic?

Recent wipes have averaged a busiest crowd of 2 players. 3 hours after the latest wipe started, the crowd hit its peak. Recent wipes kept the crowd above half that peak until the next wipe 100% of the time.

Settings and map

What settings are in place on [Uz/Ru/Kz] #2 UzRust - Classic?

Its name does not state a gather rate for [Uz/Ru/Kz] #2 UzRust - Classic. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. The server browser puts it under Modded, as plugins or settings alter the game. Oxide plugins are running here. Its own word for it is vanilla: facepunch's version, untouched: no rate changes, no kits, no extra rules. VAC, Valve's anti-cheat, is enabled.

What's the map on [Uz/Ru/Kz] #2 UzRust - Classic?

[Uz/Ru/Kz] #2 UzRust - Classic uses a procedural map of size 3,000 with seed 1974910435, made by the game. RustMaps can display it from this page because the same size and seed yield the same map.

Player count

What's the population like on [Uz/Ru/Kz] #2 UzRust - Classic?

Right now 0 players are on [Uz/Ru/Kz] #2 UzRust - Classic, which has 100 slots. For the past week, players averaged 0 with a high of 2. The busiest point in the last 48 hours was 08:00 UTC, averaging 2 players.

What's [Uz/Ru/Kz] #2 UzRust - Classic's rank among Rust servers?

[Uz/Ru/Kz] #2 UzRust - Classic ranks #5,365 for player hours over the last seven days, #377 in Asia and in the top 24% of ranked servers.

Getting in

What's the way to join [Uz/Ru/Kz] #2 UzRust - Classic?

Open Rust and press F1, then type client.connect 213.230.109.15:28025. Alternatively, click Launch Rust on this page to join via Steam. https://uzrust.uz is its website.

What each one means

Server tags

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

Game

gmrust
Game mode This is the standard Rust survival experience.
mp100
Max players It holds 100 players.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol The protocol is 2634; a different version won't get you in.
cs167781
Build It's on build 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla Facepunch's version, untouched: no rate changes, no kits, no extra rules.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Plugins or settings make changes, so it's listed as Modded.

Region

EA
East Asia The server browser lists it under East Asia.

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.