RUST METRICSFlight deck · live data
Data live Servers11,765 Players73,690 Populated3,473 Fresh wipes 3 h229 Scan5 min
‹ All servers213.230.109.15:28025
Online Full Queue Fresh wipe Wipe due No query

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

Online EA 213.230.109.15:28025 checked 9m ago

biweekly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Thu 21:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 197 SERVER FPS

Server fps

48 h low 164 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 42,725 ×1000

Entities

48 h range 42,715–44,985 · memory 6,172 MB
1239 ET SINCE RESTART 7D 19H

Uptime

7 days 19 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,276top 69% · #471 in EA
Last wipe28d agobiweekly schedule
Next wipe6d 20hThu 5 Nov, 19:00 UTC FW
Memory6,172MBat the last reading
REC 1

Players

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

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. 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

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 20hFW
  2. WPT 2Thu 12 Nov, 18:57 UTC13d 19h
  3. WPT 3Thu 26 Nov, 18:57 UTC27d 19h
  4. WPT 4Thu 3 Dec, 19:00 UTC34d 20hFW
  5. WPT 5Thu 10 Dec, 18:57 UTC41d 19h

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

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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on [Uz/Ru/Kz] #2 UzRust - Classic?

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

What wipe timing does [Uz/Ru/Kz] #2 UzRust - Classic follow?

Its tag guides the prediction: too few of [Uz/Ru/Kz] #2 UzRust - Classic's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 28 days 4 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Lists and filters

Which tags does [Uz/Ru/Kz] #2 UzRust - Classic carry, and what do they mean?

Tags published by [Uz/Ru/Kz] #2 UzRust - Classic, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe schedule; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; EA (East Asia): Its browser listing: East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show [Uz/Ru/Kz] #2 UzRust - Classic?

On Rust Metrics, [Uz/Ru/Kz] #2 UzRust - Classic sits in these lists: Modded Rust servers, checked 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.

Occupancy

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

Top 69% of all ranked servers: [Uz/Ru/Kz] #2 UzRust - Classic takes #15,276 on seven-day player hours and #471 in Asia.

What player count does [Uz/Ru/Kz] #2 UzRust - Classic carry?

Current headcount on [Uz/Ru/Kz] #2 UzRust - Classic: 0 players, 100 slots available. A seven-day average of 0 players is the reading.

Operator and location

Where does [Uz/Ru/Kz] #2 UzRust - Classic sit?

Reading: location. The EA tag puts [Uz/Ru/Kz] #2 UzRust - Classic in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 213.230.109.15:28025.

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

Rust network protocol 2634 and build 167781 on Windows is the build [Uz/Ru/Kz] #2 UzRust - Classic runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for [Uz/Ru/Kz] #2 UzRust - Classic?

Check: fps. Average 189 server fps over the last 48 hours, low of 164. Within range. Peak entity count: 44,985. Buildings, deployables and all else included. Memory peak: 6,214 MB. Lag, as players feel it, is low fps plus a climbing entity count.

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

Reading: online. [Uz/Ru/Kz] #2 UzRust - Classic answers right now. Check: restart. The uptime it reports puts the last restart about 7 days 19 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

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

No gather rate appears in the name: [Uz/Ru/Kz] #2 UzRust - Classic. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. VAC is on. That is Valve's anti-cheat.

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

From seed 1974910435, the game generates the procedural map on [Uz/Ru/Kz] #2 UzRust - Classic. Its size is 3,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto [Uz/Ru/Kz] #2 UzRust - Classic?

Check: join. Open Rust, press F1, then enter client.connect 213.230.109.15:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://uzrust.uz.

PLACARDS

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 plain Rust survival.
mp100
Max players 100 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

Region

EA
East Asia Its browser listing: 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.