Working its way up from the back of the class: #14,478 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
49/ 100
D
Slipped a little: down 189 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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.
No daily history yet.
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 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
In what location does Name of Server as Shown on the Client Server List sit?
You'll find no region listed by Name of Server as Shown on the Client Server List. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 179.64.39.123:28015.
Is Name of Server as Shown on the Client Server List up, and how steady is its uptime?
You cannot join now: Name of Server as Shown on the Client Server List is offline, last seen 38 days 6 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 21 September 2026.
On what Rust version does Name of Server as Shown on the Client Server List sit?
You will find Name of Server as Shown on the Client Server List on Rust network protocol 2633 and build 164530, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Name of Server as Shown on the Client Server List wipe its map?
There are too few wipes on record for Name of Server as Shown on the Client Server List to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 38 days 6 hours.
Player numbers
Where does Name of Server as Shown on the Client Server List sit among Rust servers?
Over the last seven days, Name of Server as Shown on the Client Server List has #14,478 for player hours, in the top 63% of all ranked servers.
What does the population on Name of Server as Shown on the Client Server List look like?
The last sighting of Name of Server as Shown on the Client Server List was 38 days 6 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Name of Server as Shown on the Client Server List?
The game's browser takes its cue from the tags Name of Server as Shown on the Client Server List has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set 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 Name of Server as Shown on the Client Server List appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Name of Server as Shown on the Client Server List: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on Name of Server as Shown on the Client Server List?
Nothing in the name of Name of Server as Shown on the Client Server List states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map Name of Server as Shown on the Client Server List uses?
Name of Server as Shown on the Client Server List runs a procedural map, which the game generates.
Connecting
How should you connect to Name of Server as Shown on the Client Server List?
To connect, start Rust, press F1, and type client.connect 179.64.39.123:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set 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 momentum (D); standing is the one to work on (F).