Rust Server IndexCard catalogue of Rust servers

Holdings11,675 servers48,366 players102 fresh wipes

Call no.EA15269 On the shelf · online

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

Online EA 213.230.109.15:28025 checked 13m ago

Subjects 1. biweekly wipes 2. vanilla3. modded4. oxide
Players now
0/ 100
0% full
7-day average
0
peak –
Rank
#15,269
top 69% · #472 in EA
Last wipeWiped1 OCT2026 · 28d 7h ago
28d ago · biweekly schedule
Next wipe
6d 16h
Thu 5 Nov, 19:00 UTC FW
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
0123403:0012:0022:0007:0016:0001:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

010020030040003:0012:0022:0007:0016:0001: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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Record sheet D · loan terms

Wipe schedule

from its schedule tag

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

Record sheet E · date due

Wipes

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

Shelf list · shelved beside it

Similar servers

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

EA
[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 14 on average
0/ 100
EA
瞌睡熊『5倍10废|10.30|萌新首选|无权限』EA · groups of 8+ · biweekly · 3 on average
3/ 100
EA
[JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 2 on average
1/ 50
EA
[JPN] Apple Server | PvP | Vanilla | 2WeeklyEA · groups of 8+ · biweekly · 2 on average
1/ 50
EA
cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 2 on average
1/ 50
EA
Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 79 on average
55/ 200
Reference desk

Quick answers

From the figures on this page.

Map and rules

On [Uz/Ru/Kz] #2 UzRust - Classic, which rules and settings apply?

The name of [Uz/Ru/Kz] #2 UzRust - Classic does not state a gather rate. The group limit is 8 players, the game's default. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. The server describes itself as vanilla: rates, kits and rules are untouched, so it plays as Facepunch made it. VAC, Valve's anti-cheat, is enabled.

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

Generated by the game, the procedural map of [Uz/Ru/Kz] #2 UzRust - Classic has size 3,000 and seed 1974910435. The map can be seen on RustMaps from this page, because the same size and seed give the same map.

Lists and filters

On Rust Server Index, which lists and filters carry [Uz/Ru/Kz] #2 UzRust - Classic?

The Rust Server Index lists that include [Uz/Ru/Kz] #2 UzRust - Classic are Modded Rust servers, filed by play style. Filed 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.

What is meant by the tags on [Uz/Ru/Kz] #2 UzRust - Classic?

These are the tags [Uz/Ru/Kz] #2 UzRust - Classic publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): The queue ceiling sits at 100; ts8 (Group limit): The team limit is 8, as in the standard game; v2634 (Protocol): Joining needs you on game protocol 2634; cs167781 (Build): Build on file: 167781; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): The region code field is left empty; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Rates, kits and rules are untouched, so it plays as Facepunch made it; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): Plugins or changed settings put this under Modded; EA (East Asia): The browser files it under East Asia. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.

Wipe schedule

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

At their busiest, its recent wipes drew 2 players on average. 3 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 100% of its recent wipes.

How often is [Uz/Ru/Kz] #2 UzRust - Classic wiped, and on what schedule?

Its schedule is unconfirmed: too few of [Uz/Ru/Kz] #2 UzRust - Classic's wipes are on record, and the prediction follows the tag. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, taken by every Rust server. Its present world dates from 28 days 7 hours. Its tags state wipes every two weeks.

Player counts

How is [Uz/Ru/Kz] #2 UzRust - Classic ranked compared with the rest?

Filed under rankings: #15,269 for [Uz/Ru/Kz] #2 UzRust - Classic on seven-day player hours, #472 in Asia, top 69% overall.

Is [Uz/Ru/Kz] #2 UzRust - Classic quiet or crowded?

The live count for [Uz/Ru/Kz] #2 UzRust - Classic stands at 0 players, out of 100 slots. Averaged over the last seven days, the count is 0 players.

Server details

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

Rust network protocol 2634 and build 167781, on Windows, is what [Uz/Ru/Kz] #2 UzRust - Classic runs. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of [Uz/Ru/Kz] #2 UzRust - Classic?

Right now [Uz/Ru/Kz] #2 UzRust - Classic is up and running. The uptime it reports puts the last restart at about 8 days ago. Uptime for the last 7 full days came to 99%, 167 hours out of 168. The earliest sighting at Rust Server Index is 13 September 2026.

Is the performance on [Uz/Ru/Kz] #2 UzRust - Classic good?

The last 48 hours give an average of 189 server fps and a floor of 164. The entity count reached 44,985, covering buildings, deployables and all else in the world. The peak memory figure stood at 6,214 MB. What players feel as lag is low fps together with a rising entity count.

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

Filed under Asia by its own listing, [Uz/Ru/Kz] #2 UzRust - Classic carries the EA tag. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 213.230.109.15:28025.

How to join

How can you connect to [Uz/Ru/Kz] #2 UzRust - Classic?

Enter client.connect 213.230.109.15:28025 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you. You will find its website at https://uzrust.uz.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp100
Max players The queue ceiling sits at 100.
ts8
Group limit The team limit is 8, as in the standard game.
v2634
Protocol Joining needs you on game protocol 2634.
cs167781
Build Build on file: 167781.
ptrak
Networking RakNet is the network layer, as standard for Rust.
$r?
Region code The region code field is left empty.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Difficulty

^v
Vanilla Rates, kits and rules are untouched, so it plays as Facepunch made it.

Mods and access

^o
Oxide Oxide, also known as uMod, provides the plugin framework.
^z
Modded Plugins or changed settings put this under Modded.

Region

EA
East Asia The browser files 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.