Skip to the story

Live edition99,159 playing on 11,894 servers

Rust Insights

Server profile · EA

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

Online, with 0 of 100 players on; ranked #10,822 of every public Rust server, the top 48%. It last wiped 27d ago.

Filed under biweekly wipes vanillamoddedoxide
Launch Rust and join Website
0/ 100 players now 0% full
07-day averagepeak 2
#10,822ranktop 48% · #437 in EA
27d agolast wipebiweekly schedule
1hnext wipeThu 29 Oct, 18:57 UTC

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
0123418:0003:0012:0021:0006:0015:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

010020030040018:0003:0012:0021:0006:0015:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

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

Note: Top 48% of all ranked servers, top 81% in EA. Ranked on player hours over the last seven days.

The wipe cycle

Wipe schedule

From its schedule tag.

Next wipe Thursday 29 October, 18:57 UTC, in 1h. Its biweekly schedule tag · low 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

  1. 1hThu 29 Oct, 18:57 UTC
  2. 7d 1hThu 5 Nov, 19:00 UTCFW
  3. 14d 1hThu 12 Nov, 18:57 UTC
  4. 28d 1hThu 26 Nov, 18:57 UTC
  5. 35d 1hThu 3 Dec, 19:00 UTCFW
  6. 42d 1hThu 10 Dec, 18:57 UTC

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

Thu 1 OctThu 17 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Note: players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.

The record

Wipes

Every wipe we saw, 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

Note: 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.

If you like this one

Similar servers

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

  1. [JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 15 on average7/100
  2. [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29EA · no group limit · biweekly · 4 on average1/20
  3. 瞌睡熊『5倍10废|10.29|萌新首选|无权限』EA · groups of 8+ · biweekly · 4 on average4/100
  4. [JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 2 on average2/50
  5. [JPN] Apple Server | PvP | Vanilla | 2WeeklyEA · groups of 8+ · biweekly · 2 on average1/50
  6. cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 2 on average1/50

The short version

Quick answers

From the figures on this page.

Wipe days

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

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

How often does [Uz/Ru/Kz] #2 UzRust - Classic wipe, and on which day?

The prediction for [Uz/Ru/Kz] #2 UzRust - Classic follows its tag, because too few of its wipes are on record to confirm the schedule. A wipe is expected on Thursday 29 October at 18:57 UTC. The world you are playing on now was made 27 days 22 hours ago. The tags give wipes as every two weeks.

Server

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

Server fps averaged 189 over 48 hours; the lowest reading was 164. Buildings, deployables and the rest took the entity count as high as 45,123. Memory use peaked at 6,214 MB. Lag, for players, is low fps and an entity count that keeps climbing.

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

Running on Windows, [Uz/Ru/Kz] #2 UzRust - Classic is on Rust network protocol 2634 and build 167781. The same protocol is required to join, and Steam takes care of updating it.

How reliable is [Uz/Ru/Kz] #2 UzRust - Classic, and is it up at the moment?

[Uz/Ru/Kz] #2 UzRust - Classic is currently reachable and online. About 7 days 13 hours ago is when it last restarted, judged from the uptime it reports. It spent 167 of the last 7 full days' 168 hours up, 99% of the time. On 13 September 2026 is when Rust Insights first saw it.

In which location does [Uz/Ru/Kz] #2 UzRust - Classic sit?

The EA tag is how [Uz/Ru/Kz] #2 UzRust - Classic places itself in Asia. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. 213.230.109.15:28025 is where it answers.

Server tags

Which meanings sit behind the tags on [Uz/Ru/Kz] #2 UzRust - Classic?

The tags gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): It holds 100 slots; ts8 (Group limit): The game default applies: teams cap at 8; v2634 (Protocol): Matching versions are required, and the protocol is 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks is the gap between wipes; ^v (Vanilla): Nothing is changed from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is filed under Modded; EA (East Asia): Its browser listing sits under East Asia are what [Uz/Ru/Kz] #2 UzRust - Classic publishes, and the server browser in the game reads them. You will find the present player count, the queue and the world's creation time among the tags, and they are displayed at the top of this page.

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

[Uz/Ru/Kz] #2 UzRust - Classic appears among the following Rust Insights lists: Modded Rust servers, explained. 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.

Population history

How many players are on [Uz/Ru/Kz] #2 UzRust - Classic right now, and how does that number move?

Of its 100 slots, [Uz/Ru/Kz] #2 UzRust - Classic currently has 0 filled. The seven-day average is 0 players, and the highest point in that week was 2.

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

In Asia, [Uz/Ru/Kz] #2 UzRust - Classic is #437; across all ranked servers it is #10,822 on seven-day player hours, in the top 48%.

Settings and rules

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

The name of [Uz/Ru/Kz] #2 UzRust - Classic does not state a gather rate. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. PvP and raiding are both enabled. Plugins or settings change the game, so it sits under Modded in the browser. It runs plugins, Oxide of them. The server describes itself as vanilla, meaning nothing is changed from Facepunch's release: no altered rates, kits or rules. The server has Valve's VAC anti-cheat switched on.

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

The game generates the map on [Uz/Ru/Kz] #2 UzRust - Classic: procedural, size 3,000, seed 1974910435. You can look at the map on RustMaps from this page, since the same size and seed produce the same map.

How to join

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

Open the console with F1 in Rust and enter client.connect 213.230.109.15:28025. You can skip the console by using Launch Rust here, which starts Rust through Steam and connects you. Its website can be found at https://uzrust.uz.

The small print

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 as standard Rust plays.
mp100
Max players It holds 100 slots.
ts8
Group limit The game default applies: teams cap at 8.
v2634
Protocol Matching versions are required, and the protocol is 2634.
cs167781
Build It runs game build 167781.
ptrak
Networking RakNet handles the network layer, as it does by default.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two weeks is the gap between wipes.

Difficulty

^v
Vanilla Nothing is changed from Facepunch's release: no altered rates, kits or rules.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is filed under Modded.

Region

EA
East Asia Its browser listing sits under East Asia.

Note: 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.