Working its way up from the back of the class: #14,600 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
31/ 100
F
Lost ground: down 5,660 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in wipe hold (A+); 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.
AveragePeakWipe
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 64% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
···F···
·······
·······
·······
···
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 gap12.2 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Thu 1 OctSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 40 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:53 UTCFW26d ago
1
–
running
1
Sat 19 Sep, 12:53 UTC39d ago
1
✓ held half
12.2 days
1
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
You'll find no region listed by ALEKSEYKA2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 82.99.41.2:28015.
How reliable is ALEKSEYKA2, and is it up?
At this moment, ALEKSEYKA2 is offline; the last time it was seen was 25 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 18 September 2026, Rust Server Score saw it for the first time.
Which Rust version is ALEKSEYKA2 running?
You will find ALEKSEYKA2 on Rust network protocol 2634 and build 166494, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does ALEKSEYKA2 wipe, and how often?
ALEKSEYKA2 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 26 days 23 hours.
What happens on ALEKSEYKA2 when wipe day arrives?
The average peak on its recent wipes was 1 players. 40 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.
Population
What position does ALEKSEYKA2 hold in the rankings?
Over the last seven days, ALEKSEYKA2 has #14,600 for player hours, in the top 64% of all ranked servers.
Is ALEKSEYKA2 a busy server?
The last sighting of ALEKSEYKA2 was 25 days 7 hours ago, and it is offline right now.
Tags
How should you read the tags on ALEKSEYKA2?
You'll see ALEKSEYKA2 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature ALEKSEYKA2?
Rust Server Score lists that include ALEKSEYKA2: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on ALEKSEYKA2?
Nothing in the name of ALEKSEYKA2 states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
ALEKSEYKA2 runs which map?
The game generates a procedural map for ALEKSEYKA2.
Connecting
What is the way to join ALEKSEYKA2?
To connect, start Rust, press F1, and type client.connect 82.99.41.2:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2634,gmrust,cs166494,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max playersThe server holds 3 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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 wipe hold (A+); momentum is the one to work on (F).