On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,366top 70%
Last wipe4d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,366 on player hours.
Uptimehours on the list, last 48
75/ 100
B
Missed a few lessons: on the list 36 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 228 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
50/ 100
D
Holding steady: down 136 places this week.
A term to build on.
Strongest in performance (A+); 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 16:12 UTC4d ago
0
–
running
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
No region is published for Carbon Test server. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 80.47.14.21:28023.
How dependable is Carbon Test server, and is it online at the moment?
At this moment, Carbon Test server is offline; the last time it was seen was 12 hours ago. The uptime it reports puts the last restart at about 3 days 12 hours ago. It was up 86 of 168 hours over the last 7 full days, which is 51% of the time. On 19 October 2026, Rust Server Score saw it for the first time.
Is Carbon Test server smooth to play on?
The average over the last 48 hours was 228 server fps, and it never went below 199. Up to 48,120 entities were in the world, covering buildings, deployables and the rest. Up to 3,126 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is Carbon Test server running?
You will find Carbon Test server on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Carbon Test server wipe its map?
There are too few wipes on record for Carbon Test server to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 4 days 1 hours have passed since this world was made.
What happens on Carbon Test server when wipe day arrives?
The average peak on its recent wipes was 0 players. Peak numbers came 0 hours into the latest wipe.
Player count
What position does Carbon Test server hold in the rankings?
In the top 70% of all ranked servers, Carbon Test server sits at #15,366 for player hours over the last seven days.
How many players does Carbon Test server usually have?
The last sighting of Carbon Test server was 12 hours ago, and it is offline right now. For the last seven days, the average number of players was 0.
Tags
What is meant by the tags on Carbon Test server?
The game's browser takes its cue from the tags Carbon Test server has set: gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): Its slot count is 100; 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): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here. 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 Carbon Test server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Carbon Test server among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Rules and settings
How is Carbon Test server set up, and what rules does it keep?
You will find no gather rate in the name of Carbon Test server. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Which map is in play on Carbon Test server?
The game generates the procedural map on Carbon Test server at size 3,000 with seed 836976. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Carbon Test server?
Enter client.connect 80.47.14.21:28023 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 asmp100,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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. Strongest in performance (A+); population is the one to work on (F).