Not ranked yet, so there is no place in the school to report.
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
49/ 100
D
Slipped a little: down 192 places this week. Nothing a good wipe can't fix.
A term to build on.
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
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. You can connect at 185.248.24.173:28015.
Is KRASNOYARSK X10 Local Test up, and how steady is its uptime?
You cannot join now: KRASNOYARSK X10 Local Test is offline, last seen 38 days 19 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
On what Rust version does KRASNOYARSK X10 Local Test sit?
Rust network protocol 2633 and build 164530 on Windows is what KRASNOYARSK X10 Local Test runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does KRASNOYARSK X10 Local Test wipe, and how often?
The record holds too few of KRASNOYARSK X10 Local Test's wipes to tell its 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 43 days 7 hours.
Player numbers
What position does KRASNOYARSK X10 Local Test hold in the rankings?
Over the last seven days, KRASNOYARSK X10 Local Test has #13,747 for player hours, in the top – of all ranked servers.
Is KRASNOYARSK X10 Local Test a busy server?
The last sighting of KRASNOYARSK X10 Local Test was 38 days 19 hours ago, and it is offline right now.
Tags and filters
What do KRASNOYARSK X10 Local Test's tags stand for?
You'll see KRASNOYARSK X10 Local Test tagged with gmrust (Game mode): Survival in the standard Rust style; mp4 (Max players): 4 slots are available; ts5 (Group limit): No team may go above 5; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. 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.
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. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 10x.
Server rules
What settings and rules apply on KRASNOYARSK X10 Local Test?
Going by its name, KRASNOYARSK X10 Local Test runs 10x gather. A group here can reach 5 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. 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.
Connecting
How should you connect to KRASNOYARSK X10 Local Test?
Enter client.connect 185.248.24.173: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 asmp4,ptrak,$r?,v2633,gmrust,cs164530,ts5,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp4
Max players4 slots are available.
ts5
Group limitNo team may go above 5.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it 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.