Working its way up from the back of the class: #14,810 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
45/ 100
D
Slipped a little: down 1,406 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); wipes are 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.
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 68% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
····W··
·······
W······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap11 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 12 OctFri 2 OctSun 20 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 20:30 UTC16d ago
1
–
running
1
Fri 2 Oct, 17:46 UTC26d ago
–
–
10.1 days
0
Sun 20 Sep, 20:59 UTC38d ago
1
halved by day 1
11.9 days
1
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 BizRust Carbon Dev. Rust Server Score takes the server's word for its location and does not trace the hardware. 95.188.66.115:28015 is the address to use.
How dependable is BizRust Carbon Dev, and is it online at the moment?
At this moment, BizRust Carbon Dev is offline; the last time it was seen was 16 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does BizRust Carbon Dev sit?
Rust network protocol 2634 and build 167584 on Windows is what BizRust Carbon Dev runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does BizRust Carbon Dev reset?
BizRust Carbon Dev wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 16 days 7 hours.
What should you expect from wipe day on BizRust Carbon Dev?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 1 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
Where does BizRust Carbon Dev place in the wider field of Rust servers?
Over the last seven days, BizRust Carbon Dev has #14,810 for player hours, in the top 68% of all ranked servers.
How many players does BizRust Carbon Dev usually have?
It has been 16 days 6 hours since BizRust Carbon Dev was last seen, and it is offline right now.
Tags and filters
How should you read the tags on BizRust Carbon Dev?
The game's browser takes its cue from the tags BizRust Carbon Dev has set: gmrust (Game mode): Rust survival, played by the standard rules; mp500 (Max players): 500 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; 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): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon. 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 BizRust Carbon Dev?
These Rust Server Score lists count BizRust 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.
Map and rules
What settings and rules apply on BizRust Carbon Dev?
Nothing in the name of BizRust Carbon Dev states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in 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. You are covered by VAC, Valve's anti-cheat.
Connecting
What is the way to join BizRust Carbon Dev?
Enter client.connect 95.188.66.115: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 asmp500,ptrak,$r?,v2634,gmrust,cs167584,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp500
Max players500 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
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
ModdedThe game is changed by plugins or settings; you will find it 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. Strongest in momentum (D); wipes are the one to work on (F).