A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
38/ 100
F
Working its way up from the back of the class: #13,729 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
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
33/ 100
F
Lost ground: down 4,692 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (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
Every five minutes, from the Steam server list.
AveragePeak
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 62% of all ranked servers, top 76% in NA. 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h.
The 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
In what location does Rob's Rust | Carbon | 3500 | Monthly sit?
In North America, according to its own listing, sits Rob's Rust | Carbon | 3500 | Monthly, with the NA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 67.221.109.225:28015 is the address to use.
How reliable is Rob's Rust | Carbon | 3500 | Monthly, and is it up?
You can join now: Rob's Rust | Carbon | 3500 | Monthly is online. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 9 October 2026.
On what Rust version does Rob's Rust | Carbon | 3500 | Monthly sit?
You will find Rob's Rust | Carbon | 3500 | Monthly on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does Rob's Rust | Carbon | 3500 | Monthly reset?
the force wipe gives the basis for estimating Rob's Rust | Carbon | 3500 | Monthly's next 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 19 days 20 hours. Its tags record that it wipes monthly.
Player count
What position does Rob's Rust | Carbon | 3500 | Monthly hold in the rankings?
Over the last seven days, Rob's Rust | Carbon | 3500 | Monthly has #13,729 for player hours, in the top 62% of all ranked servers and #1,418 in North America.
What does the population on Rob's Rust | Carbon | 3500 | Monthly look like?
With 50 slots available, Rob's Rust | Carbon | 3500 | Monthly currently has 0 players. The seven-day average is 0 players, with a peak of 1.
Tags
What do Rob's Rust | Carbon | 3500 | Monthly's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $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): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon; NA (North America): The server browser lists it under North America are the tags Rob's Rust | Carbon | 3500 | Monthly 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.
Which Rust Server Score filters and lists feature Rob's Rust | Carbon | 3500 | Monthly?
These Rust Server Score lists count Rob's Rust | Carbon | 3500 | Monthly among them: Modded Rust servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is Rob's Rust | Carbon | 3500 | Monthly set up, and what rules does it keep?
Nothing in the name of Rob's Rust | Carbon | 3500 | Monthly states a 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. 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.
Can you tell me which map Rob's Rust | Carbon | 3500 | Monthly uses?
A procedural map, generated by the game, is what Rob's Rust | Carbon | 3500 | Monthly runs.
Connecting
How should you connect to Rob's Rust | Carbon | 3500 | Monthly?
Enter client.connect 67.221.109.225: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 asmp50,ptrak,$r?,v2635,^z,^y,^m,NA,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
Region
NA
North AmericaThe server browser lists it under North America.
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 uptime (A); population is the one to work on (F).