A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
47/ 100
D
Working its way up from the back of the class: #11,809 on player hours.
Uptimehours on the list, last 48
2/ 100
F
Attendance needs work: on the list only 1 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); uptime 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.
No daily history yet.
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 53% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
No region is published for ALEKSEYKA2. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 84.15.220.143:28015.
How dependable is ALEKSEYKA2, and is it online at the moment?
At this moment, ALEKSEYKA2 is offline; the last time it was seen was 47 hours ago. For the last 1 full day, it was up 0 of 24 hours, or 0% of the time. It was first seen by Rust Server Score on 27 October 2026.
On what Rust version does ALEKSEYKA2 sit?
The server ALEKSEYKA2 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
How frequently does ALEKSEYKA2 wipe its map?
There are too few wipes on record for ALEKSEYKA2 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 2 days.
Player count
Where does ALEKSEYKA2 place in the wider field of Rust servers?
Over the last seven days, ALEKSEYKA2 has #11,809 for player hours, in the top 53% of all ranked servers.
Is ALEKSEYKA2 a busy server?
The last sighting of ALEKSEYKA2 was 47 hours ago, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. The highest average in the last 48 hours came at 16:00 UTC, with 1 players.
Tags
How should you read the tags on ALEKSEYKA2?
The game's browser takes its cue from the tags ALEKSEYKA2 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this 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 lists and filters on Rust Server Score show ALEKSEYKA2?
These Rust Server Score lists count ALEKSEYKA2 among them: 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; Last wipe: In the last 3 days.
Rules and settings
How is ALEKSEYKA2 set up, and what rules does it keep?
The name of ALEKSEYKA2 gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
ALEKSEYKA2 runs which map?
The game generates a procedural map for ALEKSEYKA2.
Getting in
What is the way to join ALEKSEYKA2?
Enter client.connect 84.15.220.143:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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); uptime is the one to work on (F).