On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,262top 69% · #472 in EA
Last wipe28d agobiweekly schedule
Next wipe6d 18hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,262 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 188 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
15/ 100
F
Lost ground: down 10,617 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 69% of all ranked servers, top 87% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
···F···
·······
·······
·······
·····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
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
6d 18hThu 5 Nov, 19:00 UTCFW
13d 18hThu 12 Nov, 18:57 UTC
27d 18hThu 26 Nov, 18:57 UTC
34d 18hThu 3 Dec, 19:00 UTCFW
41d 18hThu 10 Dec, 18:57 UTC
The first 48 hours of its last wipes
Thu 1 OctThu 17 Sep
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 UTCFW28d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does [Uz/Ru/Kz] #2 UzRust - Classic sit?
In Asia, according to its own listing, sits [Uz/Ru/Kz] #2 UzRust - Classic, with the EA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 213.230.109.15:28025.
How reliable is [Uz/Ru/Kz] #2 UzRust - Classic, and is it up?
You can join now: [Uz/Ru/Kz] #2 UzRust - Classic is online. About 7 days 21 hours ago, it restarted, based on the uptime it reports. It was up 143 of 168 hours over the last 7 full days, which is 85% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Is [Uz/Ru/Kz] #2 UzRust - Classic smooth to play on?
It never fell below 164 server fps in the last 48 hours, averaging 188. At its peak, it held 44,985 entities, including buildings, deployables and all else in the world. At its highest, it used 6,214 MB of memory. Players feel lag when fps drops and entities pile up.
What Rust version is [Uz/Ru/Kz] #2 UzRust - Classic on?
You will find [Uz/Ru/Kz] #2 UzRust - Classic on Rust network protocol 2634 and build 167781, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does [Uz/Ru/Kz] #2 UzRust - Classic wipe, and how often?
Too few wipes on [Uz/Ru/Kz] #2 UzRust - Classic are recorded to confirm the schedule, so its tag guides the prediction. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. The world it runs now was created 28 days 5 hours. Its tags give a wipe schedule of every two weeks.
What happens on [Uz/Ru/Kz] #2 UzRust - Classic when wipe day arrives?
The average peak on its recent wipes was 2 players. 3 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player numbers
Where does [Uz/Ru/Kz] #2 UzRust - Classic place in the wider field of Rust servers?
Over the last seven days, [Uz/Ru/Kz] #2 UzRust - Classic has #15,262 for player hours, in the top 69% of all ranked servers and #472 in Asia.
How many players does [Uz/Ru/Kz] #2 UzRust - Classic usually have?
Right now, 0 players are on [Uz/Ru/Kz] #2 UzRust - Classic, which has 100 slots. A seven-day average of 0 players applies here.
Tags and filters
What is meant by the tags on [Uz/Ru/Kz] #2 UzRust - Classic?
You'll see [Uz/Ru/Kz] #2 UzRust - Classic tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): The server browser lists it under East Asia in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does [Uz/Ru/Kz] #2 UzRust - Classic appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [Uz/Ru/Kz] #2 UzRust - Classic among them: Modded Rust servers, graded. It shows under the following 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.
Server rules
How is [Uz/Ru/Kz] #2 UzRust - Classic set up, and what rules does it keep?
Nothing in the name of [Uz/Ru/Kz] #2 UzRust - Classic states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [Uz/Ru/Kz] #2 UzRust - Classic uses?
The game generates the procedural map on [Uz/Ru/Kz] #2 UzRust - Classic at size 3,000 with seed 1974910435. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto [Uz/Ru/Kz] #2 UzRust - Classic?
To connect, start Rust, press F1, and type client.connect 213.230.109.15:28025. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://uzrust.uz.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^b,^v,EA,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EA
East AsiaThe server browser lists 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).