Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO G SRV11,706online PAX60,014playing OCC3,275with players WIPED 3H168
MODModded traffic
Callsign

UZR15262=

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

Online EA 213.230.109.15:28025 checked 12m ago

biweekly wipes vanillamoddedoxide
Clearance · join
Players now 0/ 100 0% full
7-day average0peak –
Rank#15,262top 69% · #472 in EA
Last wipe28d agobiweekly schedule
Next wipe6d 18hThu 5 Nov, 19:00 UTC FW
Track history

Players

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

Hourly average and peak, UTC.

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.

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.

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 6d 18h.

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

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.

Nearby traffic

Similar servers

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

  1. 01MOD
    Callsign EVN020EA · groups of 10+ · biweekly · 14 on average [JP]初心者PVPサーバー|RaidTime・ Events
    Players 0/100
  2. 02MOD
    Callsign SRV016EA · groups of 8+ · biweekly · 4 on average 瞌睡熊『5倍10废|10.30|萌新首选|无权限』
    Players 1/100
  3. 03MOD
    Callsign JPP015EA · groups of 8+ · biweekly · 2 on average [JP/PvE][BPリサーチ]MatoyServer初しん者〇
    Players 1/50
  4. 04MOD
    Callsign JPN016EA · groups of 8+ · biweekly · 2 on average [JPN] Apple Server | PvP | Vanilla | 2Weekly
    Players 2/50
  5. 05MOD
    Callsign CCZ012EA · no group limit · biweekly · 2 on average cczsbwd/solo/独狼/原倍半月清/月图/公益服
    Players 1/50
  6. 06COM
    Callsign RST015EA · groups of 16+ · biweekly · 78 on average Rustoria.co - SEA Medium
    Players 73/200
ATIS · this server

Quick answers

From the figures on this page.

Filters

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

On Rust Tracker, [Uz/Ru/Kz] #2 UzRust - Classic sits in these lists: Modded servers, tracked live. These filters surface it 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.

How should you read the tags on [Uz/Ru/Kz] #2 UzRust - Classic?

These tags are published by [Uz/Ru/Kz] #2 UzRust - Classic for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): This server runs game build 167781; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^b (Biweekly): A wipe every fortnight; ^v (Vanilla): No changed rates, kits or rules — the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; EA (East Asia): Server browser: listed under East Asia. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

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

The average peak across recent wipes: 2 players. The peak on the latest wipe came 3 hours after it. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Which wipe times are confirmed for [Uz/Ru/Kz] #2 UzRust - Classic?

[Uz/Ru/Kz] #2 UzRust - Classic's schedule is unconfirmed, too few wipes being on record, so the prediction follows its tag. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. 28 days 5 hours since this world was made. A two-weekly wipe schedule is published in its tags.

Server Details

Is [Uz/Ru/Kz] #2 UzRust - Classic up, and how does its uptime hold?

[Uz/Ru/Kz] #2 UzRust - Classic is up and online at this moment. About 7 days 21 hours ago it restarted last, based on reported uptime. 143 of 168 hours up over the last 7 full days: 85% uptime. Rust Tracker logged it first on 13 September 2026.

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

Rust network protocol 2634 and build 167781 on Windows is what [Uz/Ru/Kz] #2 UzRust - Classic runs. Steam updates it for you; your game must share the protocol to join.

Is [Uz/Ru/Kz] #2 UzRust - Classic holding performance?

Average server fps over the last 48 hours: 188, with a low of 164. Maximum entities carried: 44,985, from buildings and deployables to everything else. Memory peaked at 6,214 MB. Lag, as players experience it, comes from low fps and a rising entity count.

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

The EA tag places [Uz/Ru/Kz] #2 UzRust - Classic in Asia, by its own listing. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 213.230.109.15:28025.

Player Count

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

Tracking [Uz/Ru/Kz] #2 UzRust - Classic: 0 of 100 slots filled. Across the past seven days, 0 players on average.

Where does [Uz/Ru/Kz] #2 UzRust - Classic sit in the server rankings?

Seven-day player hours: #15,262 overall for [Uz/Ru/Kz] #2 UzRust - Classic, top 69% of ranked servers, #472 in Asia.

Settings

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

No gather rate appears in [Uz/Ru/Kz] #2 UzRust - Classic's name. 8 players per group is the game's default, and the cap holds. survival is the game mode, gather, build, raid, as the game intends. Players can raid and fight each other here. Plugins or settings change the game, and the server browser lists it under Modded. The plugin count stands at Oxide. Its label is vanilla: no changed rates, kits or rules — the game as Facepunch ships it. On: VAC, Valve's anti-cheat.

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

A procedural map of size 3,000 runs on [Uz/Ru/Kz] #2 UzRust - Classic, generated by the game from seed 1974910435. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

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

To connect: start Rust, press F1, enter client.connect 213.230.109.15:28025 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://uzrust.uz.

Transponder 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 Rust survival, standard mode.
mp100
Max players 100 slots on this server.
ts8
Group limit Default team size: 8.
v2634
Protocol Join only if your game is on protocol 2634.
cs167781
Build This server runs game build 167781.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly A wipe every fortnight.

Difficulty

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

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

Region

EA
East Asia Server browser: listed 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.