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.
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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h.
The 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 Rust Zombie Development | Carbon based in?
No region is published for Rust Zombie Development | Carbon. Rust Server Score takes the server's word for its location and does not trace the hardware. 40.160.87.92:28015 is the address to use.
Is Rust Zombie Development | Carbon up, and how steady is its uptime?
The server is down: Rust Zombie Development | Carbon is offline now, with the last sighting 44 days 4 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Rust Zombie Development | Carbon running?
Rust network protocol 2633 and build 162929 on Linux is what Rust Zombie Development | Carbon runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does Rust Zombie Development | Carbon reset?
the force wipe gives the basis for estimating Rust Zombie Development | Carbon's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 50 days 4 hours. Its tags record that it wipes monthly.
Population
Where does Rust Zombie Development | Carbon sit among Rust servers?
In the top – of all ranked servers, Rust Zombie Development | Carbon sits at #15,015 for player hours over the last seven days.
How many players does Rust Zombie Development | Carbon usually have?
It has been 44 days 4 hours since Rust Zombie Development | Carbon was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Rust Zombie Development | Carbon?
You'll see Rust Zombie Development | Carbon tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): The game build is 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^r (Roleplay): This server is for roleplay; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here 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 lists and filters on Rust Server Score show Rust Zombie Development | Carbon?
Rust Server Score lists that include Rust Zombie Development | Carbon: Modded Rust servers, graded, Roleplay servers, graded and Rust zombie servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Roleplay ^r, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does Rust Zombie Development | Carbon enforce, and what are its settings?
Nothing in the name of Rust Zombie Development | Carbon states a gather rate. The group limit stays at the game's default of 8 players. It runs roleplay, roleplay rules, towns and jobs. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. The server does not run VAC, Valve's anti-cheat.
Which map is in play on Rust Zombie Development | Carbon?
The game generates a procedural map for Rust Zombie Development | Carbon.
Getting in
How do you get onto Rust Zombie Development | Carbon?
Enter client.connect 40.160.87.92: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 asmp50,ptrak,$r?,v2633,^z,^y,^m,^r,gmrust,cs162929,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildThe game build is 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^r
RoleplayThis server is for roleplay.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.