On the class lists: F (26), with population over 48 hours and no performance mark.
Players now0/ 30% full
7-day average0peak 1
Rank#13,963top 63%
Last wipe14d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 3 on average. Plenty of space to grow.
Standingrank on player hours
37/ 100
F
Working its way up from the back of the class: #13,963 on player hours.
Uptimehours on the list, last 48
19/ 100
F
Attendance needs work: on the list only 9 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 70 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
49/ 100
D
Slipped a little: down 196 places this week. Nothing a good wipe can't fix.
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 15 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 63% 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
MY TEST SERVER | Carbon leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 120.220.76.192:14231 is the address to use.
Is MY TEST SERVER | Carbon up, and how steady is its uptime?
At this moment, MY TEST SERVER | Carbon is offline; the last time it was seen was 38 hours ago. The uptime it reports puts the last restart at about 37 hours ago. It was up 40 of 168 hours over the last 7 full days, which is 24% of the time. On 15 October 2026, Rust Server Score saw it for the first time.
How well does MY TEST SERVER | Carbon run?
It never fell below 60 server fps in the last 48 hours, averaging 70. Buildings, deployables and everything else in the world added up to as many as 114,114 entities. At its highest, it used 3,825 MB of memory. When fps is low and entities climb, that is lag to players.
Which Rust version is MY TEST SERVER | Carbon running?
Rust network protocol 2635 and build 168909 on Windows is what MY TEST SERVER | Carbon runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does MY TEST SERVER | Carbon reset?
The record holds too few of MY TEST SERVER | Carbon's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 14 days 11 hours.
Player count
Where does MY TEST SERVER | Carbon sit among Rust servers?
In the top 63% of all ranked servers, MY TEST SERVER | Carbon sits at #13,963 for player hours over the last seven days.
How many players does MY TEST SERVER | Carbon usually have?
The last sighting of MY TEST SERVER | Carbon was 38 hours ago, and it is offline right now. Averaging 0 players over seven days, it peaked at 1.
Tags
What do MY TEST SERVER | Carbon's tags stand for?
You'll see MY TEST SERVER | Carbon tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): Its slot count is 3; 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): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: 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 lists and filters on Rust Server Score show MY TEST SERVER | Carbon?
Rust Server Score lists that include MY TEST SERVER | Carbon: 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.
Server rules
How is MY TEST SERVER | Carbon set up, and what rules does it keep?
You will find no gather rate in the name of MY TEST SERVER | Carbon. The group limit stays at the game's default of 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. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map MY TEST SERVER | Carbon uses?
The game generates the procedural map on MY TEST SERVER | Carbon at size 4,500 with seed 21. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto MY TEST SERVER | Carbon?
Enter client.connect 120.220.76.192:14231 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 asmp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max playersIts slot count is 3.
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
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits 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 performance (A+); population is the one to work on (F).