Working its way up from the back of the class: #12,205 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
17/ 100
F
Lost ground: down 8,145 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (D); momentum 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 54% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap1 daysbetween real wipes
wipe-day peak4players, last three wipes
The first 48 hours of its last wipes
Fri 2 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 8 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 08:49 UTC26d ago
4
–
running
0
Thu 1 Oct, 09:52 UTC27d ago
4
–
1 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 Excelsior Uzbek Server Vanilla x2 based in?
You'll find no region listed by Excelsior Uzbek Server Vanilla x2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 159.194.240.32:28015 is the address to use.
Is Excelsior Uzbek Server Vanilla x2 up, and how steady is its uptime?
You cannot join now: Excelsior Uzbek Server Vanilla x2 is offline, last seen 23 days 14 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 20 September 2026.
On what Rust version does Excelsior Uzbek Server Vanilla x2 sit?
The server Excelsior Uzbek Server Vanilla x2 is on Rust network protocol 2634 and build 166652 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Excelsior Uzbek Server Vanilla x2 wipe its map?
The record holds too few of Excelsior Uzbek Server Vanilla x2's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 26 days 20 hours have passed since this world was made.
What should you expect from wipe day on Excelsior Uzbek Server Vanilla x2?
Recent wipes have peaked at 4 players on average. Peak numbers came 8 hours into the latest wipe.
Player numbers
Where does Excelsior Uzbek Server Vanilla x2 place in the wider field of Rust servers?
Over the last seven days, Excelsior Uzbek Server Vanilla x2 has #12,205 for player hours, in the top 54% of all ranked servers.
How many players does Excelsior Uzbek Server Vanilla x2 usually have?
Excelsior Uzbek Server Vanilla x2 is offline at the moment; the last time it was seen was 23 days 14 hours ago.
Lists and filters
How should you read the tags on Excelsior Uzbek Server Vanilla x2?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; 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; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server are the tags Excelsior Uzbek Server Vanilla x2 publishes, and the game's server browser reads them. 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 Excelsior Uzbek Server Vanilla x2 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Excelsior Uzbek Server Vanilla x2: 2x Rust servers, graded and Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
Server rules
How is Excelsior Uzbek Server Vanilla x2 set up, and what rules does it keep?
The name of Excelsior Uzbek Server Vanilla x2 points to a 2x gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Excelsior Uzbek Server Vanilla x2 runs which map?
The game generates the procedural map on Excelsior Uzbek Server Vanilla x2 at size 4,500 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to Excelsior Uzbek Server Vanilla x2?
To connect, start Rust, press F1, and type client.connect 159.194.240.32:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
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.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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 standing (D); momentum is the one to work on (F).