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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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
CarbonRustReactTest leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 185.51.127.189:28015.
How reliable is CarbonRustReactTest, and is it up?
You cannot join now: CarbonRustReactTest is offline, last seen 41 days 23 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 15 September 2026.
Which Rust version is CarbonRustReactTest running?
You will find CarbonRustReactTest on Rust network protocol 2633 and build 163794, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does CarbonRustReactTest wipe, and how often?
The record holds too few of CarbonRustReactTest's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 48 days 16 hours have passed since this world was made.
Player count
Where does CarbonRustReactTest sit among Rust servers?
In the top – of all ranked servers, CarbonRustReactTest sits at #13,263 for player hours over the last seven days.
How many players does CarbonRustReactTest usually have?
It has been 41 days 23 hours since CarbonRustReactTest was last seen, and it is offline right now.
Tags
What is meant by the tags on CarbonRustReactTest?
The game's browser takes its cue from the tags CarbonRustReactTest has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): This runs on build 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does CarbonRustReactTest appear in the Rust Server Score lists and filters?
These Rust Server Score lists count CarbonRustReactTest 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 CarbonRustReactTest enforce, and what are its settings?
The name of CarbonRustReactTest gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
CarbonRustReactTest runs which map?
CarbonRustReactTest runs a procedural map, which the game generates.
Connecting
How do you get onto CarbonRustReactTest?
To connect, start Rust, press F1, and type client.connect 185.51.127.189:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs163794,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
Not enough figures yet to write a report. Check back after a few days on the list.