[Uz/Ru/Kz] #2 UzRust - Classic
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▼−1 −100.0% from 1
- 7-day average
- 0 peak 3
- Rank
- #5,439 top 25% · #360 in EA
- Rank · 7d ago
- #4,550 ▼889 places down
- Last wipe
- 14d ago biweekly schedule
- Next wipe
- due Thu 15 Oct, 18:57 UTC
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 39 player hours, last seven days
- Map
- 3000 Procedural Map · seed 1974910435
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 2 players.
Daily average and peak, UTC.
Server performance
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 bestTop 25% of all ranked servers, top 69% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tag- usual gap
- 14.3 days between real wipes
- wipe-day peak
- 2 players, last three wipes
- crowd held
- 100% of its cycles kept half the crowd
Coming wipes
- dueThu 15 Oct, 18:57 UTC
- 13d 23hThu 29 Oct, 18:57 UTC
- 20d 23hThu 5 Nov, 19:00 UTCFW
- 27d 23hThu 12 Nov, 18:57 UTC
- 41d 23hThu 26 Nov, 18:57 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:57 UTC FW14d ago | 1 | – | running | 0 |
| Thu 17 Sep, 12:48 UTC28d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ［JP］初心者PVPサーバー｜RaidTime・ EventsEA · groups of 10+ · biweekly · 4 on average | 1/100 | ▲+1 | |
| 2 | 瞌睡熊『5倍10废|10.15|萌新首选|无权限』EA · groups of 8+ · biweekly · 3 on average | 0/100 | ▼−1−100.0% | |
| 3 | cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 1 on average | 0/50 | ▪+0 | |
| 4 | Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 65 on average | 306/350 | ▲+290+1754.5% | |
| 5 | Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 34 on average | 181/325 | ▲+171+1637.6% | |
| 6 | Japan Tokyo - Mondays|10/05|JP/KR/SEA|2週間|JumpRust.comEA · groups of 8+ · biweekly · 26 on average | 12/215 | ▲+3+34.6% |
Quick answers
from the figures on this pageServer Rules
How is [Uz/Ru/Kz] #2 UzRust - Classic configured in terms of rules and settings?
No gather rate appears in the name of [Uz/Ru/Kz] #2 UzRust - Classic. Groups can contain a maximum of 8 players, the default for the game. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are in use. Its self-description is vanilla: rust as Facepunch ships it: rates, kits and rules unchanged. VAC is active.
Which map is played on [Uz/Ru/Kz] #2 UzRust - Classic?
[Uz/Ru/Kz] #2 UzRust - Classic uses a procedural map of size 3,000 with seed 1974910435, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.
Activity
Where does [Uz/Ru/Kz] #2 UzRust - Classic sit in the rankings?
On seven-day player hours, [Uz/Ru/Kz] #2 UzRust - Classic sits at #5,439, in the top 25% across ranked servers and #360 in Asia.
What is the population on [Uz/Ru/Kz] #2 UzRust - Classic?
On [Uz/Ru/Kz] #2 UzRust - Classic, 0 players are in now, out of 100 slots. Average players over seven days: 0; peak: 3. Over the last 48 hours, the peak hour was 19:00 UTC, averaging 2 players.
Wipe Cycle
What happens on wipe day at [Uz/Ru/Kz] #2 UzRust - Classic?
Recent wipes at this server drew an average peak of 2 players. On the latest wipe, 3 hours after the wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
How often does [Uz/Ru/Kz] #2 UzRust - Classic wipe?
The schedule at [Uz/Ru/Kz] #2 UzRust - Classic cannot be confirmed from the few wipes on record, so the prediction follows its tag. On Thursday 15 October at 18:57 UTC the next wipe is due. Its world now is 14 days old. Its tags carry a wipe schedule of every two weeks.
Server Info
Where can [Uz/Ru/Kz] #2 UzRust - Classic be found?
In Asia, [Uz/Ru/Kz] #2 UzRust - Classic lists itself with the EA tag. Rust Analytics reports the location a server claims, not the machine's actual location. 213.230.109.15:28025 is its address.
What is the performance like on [Uz/Ru/Kz] #2 UzRust - Classic?
Average server fps for the last 48 hours is 197; the floor was 47. At its peak it held 45,509 entities: buildings, deployables and the rest of the world. Memory use peaked at 2,373 MB. A climbing entity count plus low fps is the lag players report.
What Rust version 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. Joining requires the same protocol on your game, which Steam updates.
How reliable is [Uz/Ru/Kz] #2 UzRust - Classic and is it currently online?
Online at this moment: [Uz/Ru/Kz] #2 UzRust - Classic. 16 hours ago is when it last restarted, judging by the uptime it reports. The last 7 full days give 100% uptime, 168 hours on out of 168. First sighting by Rust Analytics: 13 September 2026.
Tags and Rankings
How should you interpret the tags on [Uz/Ru/Kz] #2 UzRust - Classic?
These tags are published by [Uz/Ru/Kz] #2 UzRust - Classic and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): It holds 100 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167781 (Build): It runs build 167781; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set; ^b (Biweekly): One wipe every fortnight; ^v (Vanilla): Rust as Facepunch ships it: rates, kits and rules unchanged; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; EA (East Asia): The server browser files it under East Asia. The tags also carry its current players, queue and world creation time; this page shows them at the top.
[Uz/Ru/Kz] #2 UzRust - Classic appears in which of the lists and filters on Rust Analytics?
These Rust Analytics lists include [Uz/Ru/Kz] #2 UzRust - Classic: Modded Rust servers. It appears 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.
Joining the Server
What is the process to join [Uz/Ru/Kz] #2 UzRust - Classic?
Type client.connect 213.230.109.15:28025 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you. You can visit its website at https://uzrust.uz.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,^b,^v,EA,gmrust,cs167781,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs167781
ptrak
$r?
Wipe schedule
^b
Difficulty
^v
Mods and access
^o
^z
Region
EA
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.