On the class lists: F (23), with population over 48 hours and no performance mark.
Players now2/ 1002% full
7-day average1peak 3
Rank#9,205top 41% · #423 in EA
Last wipe2h agoweekly schedule
Next wipe7d 2hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
59/ 100
C−
Working its way up from the back of the class: #9,205 on player hours.
Uptimehours on the list, last 48
8/ 100
F
Attendance needs work: on the list only 4 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 223 server fps on average.
Wipeskeeping the crowd after a wipe
25/ 100
F
Needs to keep more players after wipe day: 25% of wipes kept half their crowd.
Momentumrank now against a week ago
24/ 100
F
Lost ground: down 4,759 places this week. A strong wipe could turn it round.
A term to build on.
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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 41% of all ranked servers, top 78% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···F···
···W···
·······
·······
···W
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 7d 2h.
The force wipe · high confidence
usual gap7.1 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak7players, last three wipes
crowd held25%else halves by day 4
Coming wipes
7d 2hThu 5 Nov, 19:00 UTCFW
13d 18hThu 12 Nov, 11:24 UTC
20d 18hThu 19 Nov, 11:24 UTC
27d 18hThu 26 Nov, 11:24 UTC
35d 2hThu 3 Dec, 19:00 UTCFW
41d 18hThu 10 Dec, 11:24 UTC
The first 48 hours of its last wipes
Thu 8 OctThu 1 OctThu 24 Sep
Players each hour, from the hour of the wipe. The latest peaked at 5, 20 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 11:24 UTC5h ago
–
–
running
0
Thu 8 Oct, 13:18 UTC21d ago
5
–
–
0
Thu 1 Oct, 18:30 UTCFW27d ago
8
halved by day 4
6.8 days
2
Thu 24 Sep, 13:15 UTC35d ago
7
✓ held half
7.2 days
1
Thu 17 Sep, 13:44 UTC42d ago
7
halved by day 4
7 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
Which region is [Uz/Ru/Kz] #1 UzRust - Modded based in?
In Asia, according to its own listing, sits [Uz/Ru/Kz] #1 UzRust - Modded, with the EA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 213.230.109.15:28015.
Is [Uz/Ru/Kz] #1 UzRust - Modded up, and how steady is its uptime?
Right now, [Uz/Ru/Kz] #1 UzRust - Modded is online. The uptime it reports puts the last restart at about 1 hours ago. For the last 7 full days, it was up 16 of 168 hours, or 10% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is [Uz/Ru/Kz] #1 UzRust - Modded smooth to play on?
It averaged 223 server fps over the last 48 hours, with a low of 222. Up to 69,353 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,317 MB. When fps is low and entities climb, that is lag to players.
Which Rust version is [Uz/Ru/Kz] #1 UzRust - Modded running?
The server [Uz/Ru/Kz] #1 UzRust - Modded is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [Uz/Ru/Kz] #1 UzRust - Modded reset?
Its tag sets the prediction, as the record holds too few of [Uz/Ru/Kz] #1 UzRust - Modded's wipes to confirm its schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 2 hours. The tags carry a weekly wipe schedule.
What should you expect from wipe day on [Uz/Ru/Kz] #1 UzRust - Modded?
Across its recent wipes, the busiest moments averaged 7 players. 20 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 25% of its recent wipes. Day 4 is when it sank below half in the wipes that did not hold.
Population
Where does [Uz/Ru/Kz] #1 UzRust - Modded place in the wider field of Rust servers?
Over the last seven days, [Uz/Ru/Kz] #1 UzRust - Modded has #9,205 for player hours, in the top 41% of all ranked servers and #423 in Asia.
How many players does [Uz/Ru/Kz] #1 UzRust - Modded usually have?
With 100 slots available, [Uz/Ru/Kz] #1 UzRust - Modded currently has 2 players. Averaging 1 players over seven days, it peaked at 3. The busiest time in the last 48 hours was 14:00 UTC, with an average of 3 players.
Tags and filters
How should you read the tags on [Uz/Ru/Kz] #1 UzRust - Modded?
The game's browser takes its cue from the tags [Uz/Ru/Kz] #1 UzRust - Modded has set: gmvanilla (Game mode): You play vanilla survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): It wipes weekly; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): In the server browser it appears under East Asia. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [Uz/Ru/Kz] #1 UzRust - Modded appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [Uz/Ru/Kz] #1 UzRust - Modded among them: Modded Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours.
Rules and settings
What settings and rules apply on [Uz/Ru/Kz] #1 UzRust - Modded?
The name of [Uz/Ru/Kz] #1 UzRust - Modded gives no gather rate. With no change from the game default, groups take up to 8 players. 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. The plugin count runs to Oxide. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
[Uz/Ru/Kz] #1 UzRust - Modded runs which map?
A procedural map of size 2,000 and seed 201110278, generated by the game, is what [Uz/Ru/Kz] #1 UzRust - Modded runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
What is the way to join [Uz/Ru/Kz] #1 UzRust - Modded?
To connect, start Rust, press F1, and type client.connect 213.230.109.15:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://uzrust.uz/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,^v,EA,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EA
East AsiaIn the server browser it appears 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 term to build on. Strongest in performance (A+); population is the one to work on (F).