Rust Data LabData lab · live
Live readings Servers11,898 Players102,471 Populated3,963 Fresh wipes · 3h334 Sampled every 5 min

Element card · group Vanilla · atomic number 12,883, its rank

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

Online EA 213.230.109.15:28025 checked 11m ago

biweekly wipes vanillamoddedoxide
Join the experiment
Atomic mass · players now 0/ 100 0% full Room to join
7-day average0peak 1
Rank · atomic number#12,883top 58% · #455 in EA
Last wipe27d agobiweekly schedule
Next wipe50mThu 29 Oct, 18:57 UTC
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123419:0004:0013:0022:0007:0016:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
010020030040019:0004:0013:0022:0007:0016: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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Thursday 29 October, 18:57 UTC, in 50m. 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

  1. 50mThu 29 Oct, 18:57 UTC
  2. 7d 0hThu 5 Nov, 19:00 UTCFW
  3. 14d 0hThu 12 Nov, 18:57 UTC
  4. 28d 0hThu 26 Nov, 18:57 UTC
  5. 35d 0hThu 3 Dec, 19:00 UTCFW
  6. 42d 0hThu 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:57 UTC FW27d ago 1 – running 0
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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Jp [JP]初心者PVPサーバー… 2
    [JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 15 on average 2/ 100
  2. 2 Ru [JP] RUST SOLO… 1
    [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 EA · no group limit · biweekly · 4 on average 1/ 20
  3. 3 瞌睡 瞌睡熊『5倍10废|10.2… 2
    瞌睡熊『5倍10废|10.29|萌新首选|无权限』 EA · groups of 8+ · biweekly · 4 on average 2/ 100
  4. 4 Bp [JP/PvE][BPリサー… 0
    [JP/PvE][BPリサーチ]MatoyServer初しん者〇 EA · groups of 8+ · biweekly · 2 on average 0/ 50
  5. 5 Ap [JPN] Apple Se… 1
    [JPN] Apple Server | PvP | Vanilla | 2Weekly EA · groups of 8+ · biweekly · 2 on average 1/ 50
  6. 6 Cc cczsbwd/solo/独… 1
    cczsbwd/solo/独狼/原倍半月清/月图/公益服 EA · no group limit · biweekly · 2 on average 1/ 50

Quick answers

from the figures on this page

Server setup

What map is in play on [Uz/Ru/Kz] #2 UzRust - Classic?

A procedural map of size 3,000 with seed 1974910435 runs on [Uz/Ru/Kz] #2 UzRust - Classic, generated by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

How is [Uz/Ru/Kz] #2 UzRust - Classic configured, and what rules apply?

The name of [Uz/Ru/Kz] #2 UzRust - Classic carries no gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, raiding, building and gathering: the standard game. Fighting and raiding between players are allowed. In the server browser it sits under Modded: the game is changed by plugins or settings. Oxide plugins are running on it. By its own description it is vanilla: facepunch's game, with no altered rates, kits or rules. Anti-cheat is on: Valve's VAC.

Server details

Which location is [Uz/Ru/Kz] #2 UzRust - Classic based in?

With its EA tag, [Uz/Ru/Kz] #2 UzRust - Classic places itself in Asia. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. 213.230.109.15:28025 is the address it uses.

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

Rust network protocol 2634 and build 167781 on Windows is what [Uz/Ru/Kz] #2 UzRust - Classic uses. Your game needs to match the protocol to join, and Steam updates it automatically.

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

Right now, [Uz/Ru/Kz] #2 UzRust - Classic is reachable. About 7 days 14 hours ago is when it last restarted, based on its uptime. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. It first appeared to Rust Data Lab on 13 September 2026.

Does [Uz/Ru/Kz] #2 UzRust - Classic hold a steady performance?

In the last 48 hours, it averaged 188 server fps, with a low of 164. The entity count reached 45,123, including buildings, deployables and all other world items. Memory use peaked at 6,214 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe days

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

Its tag guides the prediction, since [Uz/Ru/Kz] #2 UzRust - Classic's record holds too few wipes to confirm a schedule. The wipe after this one is due on Thursday 29 October at 18:57 UTC. The world it is running now dates from 27 days 23 hours ago. Its tags list a wipe schedule of one wipe every two weeks.

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

At their busiest, recent wipes averaged 2 players. 3 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of recent wipes.

Where it appears

What should you understand from the tags [Uz/Ru/Kz] #2 UzRust - Classic carries?

gmrust (Game mode): Standard Rust survival is the game here; mp100 (Max players): 100 is the slot count; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs167781 (Build): It runs build 167781; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^b (Biweekly): The map wipes on a two-week cycle; ^v (Vanilla): Facepunch's game, with no altered rates, kits or rules; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): Because plugins or settings change the game, it is filed under Modded; EA (East Asia): In the browser it sits under East Asia: that is the tag list [Uz/Ru/Kz] #2 UzRust - Classic publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

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

These themed Rust Data Lab lists carry [Uz/Ru/Kz] #2 UzRust - Classic: Modded Rust servers, measured. Applying these filters on the server list returns it: 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.

Player counts

What position does [Uz/Ru/Kz] #2 UzRust - Classic hold among Rust servers?

[Uz/Ru/Kz] #2 UzRust - Classic is #12,883 on seven-day player hours, #455 in Asia, and in the top 58% of all ranked servers.

How many players does [Uz/Ru/Kz] #2 UzRust - Classic have at the moment?

Of 100 slots, 0 are taken on [Uz/Ru/Kz] #2 UzRust - Classic right now. A seven-day sample gives 0 players on average and 1 at the top.

Connection

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

In Rust, press F1 and enter client.connect 213.230.109.15:28025. Or click Launch Rust here to open Rust via Steam and connect automatically. For more, visit https://uzrust.uz.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp100
Max players 100 is the slot count.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs167781
Build It runs build 167781.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code The region field is left blank.

Wipe schedule

^b
Biweekly The map wipes on a two-week cycle.

Difficulty

^v
Vanilla Facepunch's game, with no altered rates, kits or rules.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.
^z
Modded Because plugins or settings change the game, it is filed under Modded.

Region

EA
East Asia In the browser it sits 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.