Rust Server TrendsSeismic network · station log
Recording Stations11,765 Players73,690 Active3,473 Wipes · 3 h229 48 h

Station EA-15276 · recording

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

Online EA 213.230.109.15:28025 checked 7m ago

biweekly wipes vanillamoddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak –
Rank
#15,276
top 69% · #471 in EA
Last wipe
28d ago
biweekly schedule
Next wipe
6d 20h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station EA-15276 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040023:0008:0017:0003:0012:0021: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. The force wipe · high confidence

usual gap
14.3 daysbetween real wipes
wipe-day peak
2players, last three wipes
crowd held
100%of its cycles kept half the crowd

Coming wipes

  1. 6d 20hThu 5 Nov, 19:00 UTCFW
  2. 13d 19hThu 12 Nov, 18:57 UTC
  3. 27d 19hThu 26 Nov, 18:57 UTC
  4. 34d 20hThu 3 Dec, 19:00 UTCFW
  5. 41d 19hThu 10 Dec, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 1 Oct, 18:57 UTC FW28d ago M0.0rising 1 – running 0
Thu 17 Sep, 12:48 UTC42d ago M0.3rising 2 held half 14.3 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 14 on average
1/ 100
瞌睡熊『5倍10废|10.30|萌新首选|无权限』 EA · groups of 8+ · biweekly · 4 on average
1/ 100
[JPN] Apple Server | PvP | Vanilla | 2Weekly EA · groups of 8+ · biweekly · 2 on average
1/ 50
[JP/PvE][BPリサーチ]MatoyServer初しん者〇 EA · groups of 8+ · biweekly · 2 on average
3/ 50
cczsbwd/solo/独狼/原倍半月清/月图/公益服 EA · no group limit · biweekly · 2 on average
1/ 50
Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 77 on average
105/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on [Uz/Ru/Kz] #2 UzRust - Classic?

Generated by the game, the map on [Uz/Ru/Kz] #2 UzRust - Classic is procedural, size 3,000 with seed 1974910435. From this page you can look at it on RustMaps, since the same size and seed give the same map.

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

The name of [Uz/Ru/Kz] #2 UzRust - Classic gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on [Uz/Ru/Kz] #2 UzRust - Classic?

A reading taken now shows 0 players on [Uz/Ru/Kz] #2 UzRust - Classic, which has 100 slots. The population averaged 0 players over the past week.

How does [Uz/Ru/Kz] #2 UzRust - Classic rank against other Rust servers?

The last seven days of player hours place [Uz/Ru/Kz] #2 UzRust - Classic at #15,276, in the top 69% of all ranked servers and #471 in Asia.

Server details

How reliably does [Uz/Ru/Kz] #2 UzRust - Classic stay online?

As recorded now, [Uz/Ru/Kz] #2 UzRust - Classic is running. Going by the uptime figure it reports, it restarted about 7 days 19 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. 13 September 2026 is when Rust Server Trends first recorded it.

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

Its average server fps over the last 48 hours was 189, and it never dropped below 164. The world held up to 44,985 entities at its peak, buildings and deployables included. It reached a ceiling of 6,214 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Where in the world is [Uz/Ru/Kz] #2 UzRust - Classic hosted?

The EA tag is how [Uz/Ru/Kz] #2 UzRust - Classic lists itself in Asia. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 213.230.109.15:28025 is the address it uses.

Which Rust version is [Uz/Ru/Kz] #2 UzRust - Classic running?

On Windows, [Uz/Ru/Kz] #2 UzRust - Classic runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on [Uz/Ru/Kz] #2 UzRust - Classic?

On average, the busiest point of its recent wipes drew 2 players. The peak on the most recent wipe came 3 hours after the wipe. Half that peak was held until the next wipe in 100% of its recent wipes.

How often does [Uz/Ru/Kz] #2 UzRust - Classic wipe, and on which days?

The prediction follows its tag, because too few of [Uz/Ru/Kz] #2 UzRust - Classic's wipes are on record to confirm its schedule. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 28 days 4 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.

Server tags

What do the server tags on [Uz/Ru/Kz] #2 UzRust - Classic mean?

The game's server browser reads the tags [Uz/Ru/Kz] #2 UzRust - Classic publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^b (Biweekly): A wipe comes every second week; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): East Asia is the region it's listed under in the browser. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does [Uz/Ru/Kz] #2 UzRust - Classic appear?

The Rust Server Trends lists that take in [Uz/Ru/Kz] #2 UzRust - Classic are: Modded Rust servers, tracked live. 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.

Connecting

What steps get you onto [Uz/Ru/Kz] #2 UzRust - Classic?

To join, enter client.connect 213.230.109.15:28025 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://uzrust.uz.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players 100 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build It runs game build 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Wipe schedule

^b
Biweekly A wipe comes every second week.

Difficulty

^v
Vanilla Unchanged from Facepunch's release: no altered rates, kits or rules.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Region

EA
East Asia East Asia is the region it's listed under in the 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.