On the class lists: D (48), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average1peak 1
Rank#11,541top 52%
Last wipe4d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
10/ 100
F
A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
48/ 100
D
Working its way up from the back of the class: #11,541 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); population is the one to work on (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 52% 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
In what location does Combat Local - Carbon Dev sit?
No region is published for Combat Local - Carbon Dev. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 213.182.203.76:28015 is the address to use.
How reliable is Combat Local - Carbon Dev, and is it up?
The server is down: Combat Local - Carbon Dev is offline now, with the last sighting 4 days 9 hours ago. It was up 0% of the time over the last 4 full days, 0 of 96 hours. It was first seen by Rust Server Score on 24 October 2026.
On what Rust version does Combat Local - Carbon Dev sit?
Rust network protocol 2635 and build 168909 on Windows is what Combat Local - Carbon Dev runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Combat Local - Carbon Dev wipe its map?
The record holds too few of Combat Local - Carbon Dev's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 4 days 15 hours.
Player numbers
Where does Combat Local - Carbon Dev sit among Rust servers?
Over the last seven days, Combat Local - Carbon Dev has #11,541 for player hours, in the top 52% of all ranked servers.
How many players does Combat Local - Carbon Dev usually have?
The last sighting of Combat Local - Carbon Dev was 4 days 9 hours ago, and it is offline right now. Averaging 1 players over seven days, it peaked at 1.
Lists and filters
What do Combat Local - Carbon Dev's tags stand for?
You'll see Combat Local - Carbon Dev tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; 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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Combat Local - Carbon Dev?
These Rust Server Score lists count Combat Local - Carbon Dev 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; Last wipe: In the last week.
Rules and settings
What settings and rules apply on Combat Local - Carbon Dev?
You will find no gather rate in the name of Combat Local - Carbon Dev. 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. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Connecting
How do you get onto Combat Local - Carbon Dev?
To connect, start Rust, press F1, and type client.connect 213.182.203.76:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
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. Strongest in standing (D); population is the one to work on (F).