Working its way up from the back of the class: #13,064 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
32/ 100
F
Lost ground: down 4,612 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 59% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
·W·····
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h.
The force wipe · high confidence
usual gap16.5 daysbetween real wipes
wipe-day peak0players, last three wipes
Coming wipes
7d 5hThu 5 Nov, 19:00 UTCFW
35d 5hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Tue 13 OctSun 27 Sep
Players each hour, from the hour of the wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 13 Oct, 23:01 UTC15d ago
–
–
running
0
Sun 27 Sep, 11:32 UTC32d ago
0
–
16.5 days
0
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
You'll find no region listed by Local Carbon. Rust Server Score takes the server's word for its location and does not trace the hardware. 85.234.100.50:28015 is the address to use.
How dependable is Local Carbon, and is it online at the moment?
At this moment, Local Carbon is offline; the last time it was seen was 8 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 25 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Local Carbon sit?
The server Local Carbon is on Rust network protocol 2634 and build 167781 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Local Carbon wipe, and how often?
Once a month, Local Carbon wipes with the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 15 days 14 hours. The tags show a monthly wipe schedule.
What happens on Local Carbon when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players.
Player numbers
Where does Local Carbon sit among Rust servers?
Over the last seven days, Local Carbon has #13,064 for player hours, in the top 59% of all ranked servers.
Is Local Carbon a busy server?
It has been 8 days 20 hours since Local Carbon was last seen, and it is offline right now.
Tags
What do Local Carbon's tags stand for?
gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): Its slot count is 10; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags Local Carbon publishes, and the game's server browser reads them. 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 Local Carbon appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Local Carbon among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does Local Carbon enforce, and what are its settings?
The name of Local Carbon gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Local Carbon runs which map?
The game generates a procedural map for Local Carbon.
How to join
What is the way to join Local Carbon?
Enter client.connect 85.234.100.50: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 asmp10,ptrak,$r?,v2634,^z,^y,^m,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp10
Max playersIts slot count is 10.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Even marks across the subjects, from F to F.