Working its way up from the back of the class: #13,164 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
38/ 100
F
Slipped a little: down 3,077 places this week. Nothing a good wipe can't fix.
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.
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 61% 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?
No region is published for Name of Server as Shown on the Client Server List. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 58.11.24.16:28015.
How reliable is Name of Server as Shown on the Client Server List, and is it up?
You cannot join now: Name of Server as Shown on the Client Server List is offline, last seen 15 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Name of Server as Shown on the Client Server List running?
Rust network protocol 2634 and build 167781 on Windows is what Name of Server as Shown on the Client Server List runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does Name of Server as Shown on the Client Server List reset?
There are too few wipes on record for Name of Server as Shown on the Client Server List to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 15 days 17 hours have passed since this world was made.
Population
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 #13,164 for player hours, in the top 61% of all ranked servers.
How many players does Name of Server as Shown on the Client Server List usually have?
The last sighting of Name of Server as Shown on the Client Server List was 15 days 12 hours ago, and it is offline right now.
Tags
What do Name of Server as Shown on the Client Server List's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here are the tags Name of Server as Shown on the Client Server List publishes, and the game's server browser reads them. 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.
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.
Map and rules
Which rules does Name of Server as Shown on the Client Server List enforce, and what are its settings?
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. It runs survival, 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 covered by VAC, Valve's anti-cheat.
Can you tell me which map Name of Server as Shown on the Client Server List uses?
The game generates a procedural map for Name of Server as Shown on the Client Server List.
Connecting
How should you connect to Name of Server as Shown on the Client Server List?
Enter client.connect 58.11.24.16: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 asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
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. Even marks across the subjects, from F to F.