On the class lists: D (46), with population over 48 hours and no performance mark.
Players now0/ 5000% full
7-day average1peak 1
Rank#12,015top 54%
Last wipe11d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 1 of 500 on average. Plenty of space to grow.
Standingrank on player hours
46/ 100
D
Working its way up from the back of the class: #12,015 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.
AveragePeak
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 54% 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
BizRust Carbon Dev leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 136.148.222.49:28015 is the address to use.
Is BizRust Carbon Dev up, and how steady is its uptime?
You cannot join now: BizRust Carbon Dev is offline, last seen 5 days 20 hours ago. It was up 2 of 120 hours over the last 5 full days, which is 2% of the time. The first sighting by Rust Server Score was on 22 October 2026.
What Rust version is BizRust Carbon Dev on?
The server BizRust Carbon Dev is on Rust network protocol 2635 and build 168909 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does BizRust Carbon Dev wipe, and how often?
BizRust Carbon Dev has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 11 days 23 hours have passed since this world was made.
Player count
Where does BizRust Carbon Dev sit among Rust servers?
Over the last seven days, BizRust Carbon Dev has #12,015 for player hours, in the top 54% of all ranked servers.
How many players does BizRust Carbon Dev usually have?
It has been 5 days 20 hours since BizRust Carbon Dev was last seen, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days.
Tags
What is meant by the tags on BizRust Carbon Dev?
The game's browser takes its cue from the tags BizRust Carbon Dev has set: gmrust (Game mode): Survival in the standard Rust style; mp500 (Max players): Its slot count is 500; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does BizRust Carbon Dev appear in the Rust Server Score lists and filters?
These Rust Server Score lists count BizRust Carbon Dev among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is BizRust Carbon Dev set up, and what rules does it keep?
The name of BizRust Carbon Dev gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
How to join
What is the way to join BizRust Carbon Dev?
Enter client.connect 136.148.222.49: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?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp500
Max playersIts slot count is 500.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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).