Working its way up from the back of the class: #12,997 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
44/ 100
F
Slipped a little: down 1,502 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 59% 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
Which region is KRASNOYARSK X10 Local Test based in?
KRASNOYARSK X10 Local Test leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 89.105.222.218:28015 is the address to use.
Is KRASNOYARSK X10 Local Test up, and how steady is its uptime?
The server is down: KRASNOYARSK X10 Local Test is offline now, with the last sighting 12 days ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 17 October 2026.
On what Rust version does KRASNOYARSK X10 Local Test sit?
The server KRASNOYARSK X10 Local Test is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does KRASNOYARSK X10 Local Test reset?
KRASNOYARSK X10 Local Test 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 12 days 1 hours.
Player numbers
Where does KRASNOYARSK X10 Local Test place in the wider field of Rust servers?
Over the last seven days, KRASNOYARSK X10 Local Test has #12,997 for player hours, in the top 59% of all ranked servers.
What does the population on KRASNOYARSK X10 Local Test look like?
It has been 12 days since KRASNOYARSK X10 Local Test was last seen, and it is offline right now.
Tags and filters
How should you read the tags on KRASNOYARSK X10 Local Test?
You'll see KRASNOYARSK X10 Local Test tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp4 (Max players): 4 slots are available; ts5 (Group limit): Teams cap out at 5; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon 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 KRASNOYARSK X10 Local Test?
Rust Server Score lists that include KRASNOYARSK X10 Local Test: 10x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 10x.
Rules and settings
How is KRASNOYARSK X10 Local Test set up, and what rules does it keep?
The name of KRASNOYARSK X10 Local Test points to a 10x gather rate. You can play in groups of up to 5 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map KRASNOYARSK X10 Local Test uses?
The game generates a procedural map for KRASNOYARSK X10 Local Test.
How to join
What is the way to join KRASNOYARSK X10 Local Test?
To connect, start Rust, press F1, and type client.connect 89.105.222.218:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp4,ptrak,$r?,v2634,gmrust,cs167781,ts5,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp4
Max players4 slots are available.
ts5
Group limitTeams cap out at 5.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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. Even marks across the subjects, from F to F.