Working its way up from the back of the class: #15,905 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
52/ 100
D
Moving up: up 634 places this week.
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.
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak5players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 21 Sep, 15:38 UTC36d ago
5
–
running
1
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
your_server_name leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 92.208.231.11:28015.
How dependable is your_server_name, and is it online at the moment?
At this moment, your_server_name is offline; the last time it was seen was 25 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 21 September 2026.
Which Rust version is your_server_name running?
The server your_server_name is on Rust network protocol 2633 and build 164530 under Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does your_server_name wipe its map?
your_server_name 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 36 days 10 hours.
What happens on your_server_name when wipe day arrives?
The average peak on its recent wipes was 5 players. The crowd on the latest wipe was largest 1 hours after it began.
Player numbers
Where does your_server_name sit among Rust servers?
In the top 70% of all ranked servers, your_server_name sits at #15,905 for player hours over the last seven days.
What does the population on your_server_name look like?
The last sighting of your_server_name was 25 days 11 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on your_server_name?
You'll see your_server_name tagged with gmrust (Game mode): Survival in the standard Rust style; mp8 (Max players): 8 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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 Rust Server Score filters and lists feature your_server_name?
These Rust Server Score lists count your_server_name among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does your_server_name enforce, and what are its settings?
You will find no gather rate in the name of your_server_name. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
your_server_name runs which map?
A procedural map, generated by the game, is what your_server_name runs.
Getting in
What is the way to join your_server_name?
To connect, start Rust, press F1, and type client.connect 92.208.231.11:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp8
Max players8 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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. Strongest in momentum (D); standing is the one to work on (F).