Working its way up from the back of the class: #14,042 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
37/ 100
F
Slipped a little: down 3,735 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 84.189.206.54:28015.
How reliable is Name of Server as Shown on the Client Server List, and is it up?
At this moment, Name of Server as Shown on the Client Server List is offline; the last time it was seen was 33 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 25 September 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?
You will find Name of Server as Shown on the Client Server List on Rust network protocol 2633 and build 163794, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Name of Server as Shown on the Client Server List wipe, and how often?
Name of Server as Shown on the Client Server List has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 38 days 23 hours.
Population
Where does Name of Server as Shown on the Client Server List place in the wider field of Rust servers?
In the top 61% of all ranked servers, Name of Server as Shown on the Client Server List sits at #14,042 for player hours over the last seven days.
How many players does Name of Server as Shown on the Client Server List usually have?
It has been 33 days 21 hours since Name of Server as Shown on the Client Server List was last seen, and it is offline right now.
Tags and filters
What do Name of Server as Shown on the Client Server List's tags stand for?
You'll see Name of Server as Shown on the Client Server List tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): Build number: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. 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 Name of Server as Shown on the Client Server List?
These Rust Server Score lists count Name of Server as Shown on the Client Server List among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is Name of Server as Shown on the Client Server List set up, and what rules does it keep?
You will find no gather rate in the name of Name of Server as Shown on the Client Server List. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Connecting
How should you connect to Name of Server as Shown on the Client Server List?
Enter client.connect 84.189.206.54: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?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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.