Rust PopulationField survey · Rust servers
Observing 60,014 players 11,706 servers 3,275 with someone on 160 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,262EAfirst seen 13 Sep 2026

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

Online EA 213.230.109.15:28025 checked 20m ago

biweekly wipes vanillamoddedoxide

Measurements

Players now
0/ 100
0% full
7-day average
0
peak –
Rank
#15,262
top 69% · #472 in EA
Last wipe
28d ago
biweekly schedule
Next wipe
6d 18h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

AveragePeak
0123401:0010:0020:0005:0014:0023:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

010020030040001:0010:0020:0005:0014:0023: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.

Obs. 3 · standing

Rank

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

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

Obs. 4 · the wipe cycle

Wipe schedule

from its schedule tag

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

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

Coming wipes

6d 18h
Thu 5 Nov, 19:00 UTC
FW
13d 18h
Thu 12 Nov, 18:57 UTC
27d 18h
Thu 26 Nov, 18:57 UTC
34d 18h
Thu 3 Dec, 19:00 UTC
FW
41d 18h
Thu 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.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:57 UTC FW28d 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.

Field questions

Quick answers

from the figures on this page

Player counts

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

On player hours over the last seven days [Uz/Ru/Kz] #2 UzRust - Classic is #15,262, #472 in Asia, placing it in the top 69% of ranked servers.

How busy is [Uz/Ru/Kz] #2 UzRust - Classic?

[Uz/Ru/Kz] #2 UzRust - Classic holds 0 players at the moment, out of 100 slots. A seven-day average of 0 players was counted here.

Lists and tags

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

What the game's server browser reads from [Uz/Ru/Kz] #2 UzRust - Classic is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): You can join up to 100 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded; EA (East Asia): The server browser lists it under East Asia. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include [Uz/Ru/Kz] #2 UzRust - Classic?

These Rust Population lists include [Uz/Ru/Kz] #2 UzRust - Classic: Modded Rust servers, counted. Look for it under these filters 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.

Wipe schedule

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

The busiest point of its recent wipes averaged 2 players. 3 hours after the latest wipe the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

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

Its tag sets the prediction: too few of [Uz/Ru/Kz] #2 UzRust - Classic's wipes are on record to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe, which takes every Rust server. Counted from 28 days 5 hours ago, that is how long the current world has stood. The tags carry an every-two-weeks wipe schedule.

Settings

Which map does [Uz/Ru/Kz] #2 UzRust - Classic run?

A procedural map of size 3,000 from seed 1974910435, generated by the game, is in use on [Uz/Ru/Kz] #2 UzRust - Classic. You can look at it on RustMaps from this page: size and seed determine the map.

What are the rules and settings on [Uz/Ru/Kz] #2 UzRust - Classic?

The name tells you nothing about gather rates: [Uz/Ru/Kz] #2 UzRust - Classic states none. No limit is set beyond the standard 8 players per group. survival is what it runs, gather, build and raid, as in the standard game. You can raid and fight other players here. Modded is its browser category: plugins or settings change the game. The plugins it runs are Oxide. By its own description it is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. The anti-cheat VAC from Valve is enabled.

About the server

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

On Windows, [Uz/Ru/Kz] #2 UzRust - Classic runs Rust network protocol 2634 and build 167781. Your game needs the same protocol to join; Steam takes care of updating it.

Does [Uz/Ru/Kz] #2 UzRust - Classic run smoothly?

In the last 48 hours, it averaged 188 server fps, with a low of 164. Up to 44,985 entities were present, counting buildings, deployables and everything else. Up to 6,214 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.

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

[Uz/Ru/Kz] #2 UzRust - Classic is up and running at the moment. Judging by the uptime it reports, the last restart was about 7 days 21 hours ago. Over the last 7 full days, 143 of 168 hours were online, or 85%. The first sighting by Rust Population was on 13 September 2026.

Where is [Uz/Ru/Kz] #2 UzRust - Classic located?

With its EA tag, [Uz/Ru/Kz] #2 UzRust - Classic places itself in Asia. Rust Population does not look up where the machine stands; it shows where the server says it is. You will find it at 213.230.109.15:28025.

Getting in

How do I join [Uz/Ru/Kz] #2 UzRust - Classic?

Either enter client.connect 213.230.109.15:28025 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected. You can find its website at https://uzrust.uz.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players You can join up to 100 slots.
ts8
Group limit 8 per team is the default limit.
v2634
Protocol To join, your game must match protocol 2634.
cs167781
Build Game build: 167781.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code No region code is set.

Wipe schedule

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

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded The game is changed by plugins or settings, so it is listed under 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.