Working its way up from the back of the class: #15,122 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
23/ 100
F
Lost ground: down 8,179 places this week. A strong wipe could turn it round.
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.
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 69% 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
Sector 17 - Carbon Test leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 62.118.108.250:28015.
How dependable is Sector 17 - Carbon Test, and is it online at the moment?
The server is down: Sector 17 - Carbon Test is offline now, with the last sighting 11 days 3 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 14 October 2026.
Which Rust version is Sector 17 - Carbon Test running?
Rust network protocol 2634 and build 167584 on Windows is what Sector 17 - Carbon Test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Sector 17 - Carbon Test wipe its map?
Sector 17 - Carbon 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. The world it runs now was created 15 days 7 hours.
Player count
Where does Sector 17 - Carbon Test sit among Rust servers?
Over the last seven days, Sector 17 - Carbon Test has #15,122 for player hours, in the top 69% of all ranked servers.
What does the population on Sector 17 - Carbon Test look like?
Sector 17 - Carbon Test is offline at the moment; the last time it was seen was 11 days 3 hours ago.
Lists and filters
What is meant by the tags on Sector 17 - Carbon Test?
gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon are the tags Sector 17 - Carbon Test 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.
Which lists and filters on Rust Server Score show Sector 17 - Carbon Test?
These Rust Server Score lists count Sector 17 - Carbon Test among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
Which rules does Sector 17 - Carbon Test enforce, and what are its settings?
The name of Sector 17 - Carbon Test gives no gather rate. With no change from the game default, groups take up to 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 as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Sector 17 - Carbon Test runs which map?
The game generates a procedural map for Sector 17 - Carbon Test.
How to join
What is the way to join Sector 17 - Carbon Test?
To connect, start Rust, press F1, and type client.connect 62.118.108.250:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,gmrust,cs167584,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167584
BuildBuild number: 167584.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: 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.