Working its way up from the back of the class: #16,736 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
30/ 100
F
Lost ground: down 6,794 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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 70% 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
In what location does NimbusChill's Server | Wipe 9/3/26 | Vanilla sit?
You'll find no region listed by NimbusChill's Server | Wipe 9/3/26 | Vanilla. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 204.244.253.216:28015.
Is NimbusChill's Server | Wipe 9/3/26 | Vanilla up, and how steady is its uptime?
At this moment, NimbusChill's Server | Wipe 9/3/26 | Vanilla is offline; the last time it was seen was 29 days 2 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 29 September 2026.
Which Rust version is NimbusChill's Server | Wipe 9/3/26 | Vanilla running?
Rust network protocol 2633 and build 165217 on Windows is what NimbusChill's Server | Wipe 9/3/26 | Vanilla runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does NimbusChill's Server | Wipe 9/3/26 | Vanilla reset?
NimbusChill's Server | Wipe 9/3/26 | Vanilla has not had enough wipes recorded to reveal 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 55 days 12 hours.
Population
What position does NimbusChill's Server | Wipe 9/3/26 | Vanilla hold in the rankings?
In the top 70% of all ranked servers, NimbusChill's Server | Wipe 9/3/26 | Vanilla sits at #16,736 for player hours over the last seven days.
How many players does NimbusChill's Server | Wipe 9/3/26 | Vanilla usually have?
NimbusChill's Server | Wipe 9/3/26 | Vanilla is offline at the moment; the last time it was seen was 29 days 2 hours ago.
Tags
How should you read the tags on NimbusChill's Server | Wipe 9/3/26 | Vanilla?
You'll see NimbusChill's Server | Wipe 9/3/26 | Vanilla tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show NimbusChill's Server | Wipe 9/3/26 | Vanilla?
Rust Server Score lists that include NimbusChill's Server | Wipe 9/3/26 | Vanilla: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does NimbusChill's Server | Wipe 9/3/26 | Vanilla enforce, and what are its settings?
You will find no gather rate in the name of NimbusChill's Server | Wipe 9/3/26 | Vanilla. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map NimbusChill's Server | Wipe 9/3/26 | Vanilla uses?
NimbusChill's Server | Wipe 9/3/26 | Vanilla runs a procedural map, which the game generates.
Connecting
What is the way to join NimbusChill's Server | Wipe 9/3/26 | Vanilla?
To connect, start Rust, press F1, and type client.connect 204.244.253.216:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max players2 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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. Even marks across the subjects, from F to F.