Working its way up from the back of the class: #14,329 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
33/ 100
F
Lost ground: down 4,873 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.
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 64% 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.
usual gap0.3 daysbetween real wipes
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Tue 6 OctTue 6 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 6 Oct, 18:53 UTC22d ago
2
–
running
2
Tue 6 Oct, 12:17 UTC23d ago
2
–
0.3 days
0
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
#1 MyRustServer leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 185.241.225.51:28015 is the address to use.
How reliable is #1 MyRustServer, and is it up?
The server is down: #1 MyRustServer is offline now, with the last sighting 22 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 30 September 2026, Rust Server Score saw it for the first time.
What Rust version is #1 MyRustServer on?
Rust network protocol 2634 and build 167058 on Windows is what #1 MyRustServer runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does #1 MyRustServer wipe, and how often?
The record holds too few of #1 MyRustServer's wipes to tell 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 22 days 23 hours.
What happens on #1 MyRustServer when wipe day arrives?
The average peak on its recent wipes was 2 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does #1 MyRustServer place in the wider field of Rust servers?
Over the last seven days, #1 MyRustServer has #14,329 for player hours, in the top 64% of all ranked servers.
What does the population on #1 MyRustServer look like?
#1 MyRustServer is offline at the moment; the last time it was seen was 22 days 4 hours ago.
Lists and filters
What do #1 MyRustServer's tags stand for?
The game's browser takes its cue from the tags #1 MyRustServer has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $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. 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 #1 MyRustServer appear in the Rust Server Score lists and filters?
Rust Server Score lists that include #1 MyRustServer: 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
What settings and rules apply on #1 MyRustServer?
You will find no gather rate in the name of #1 MyRustServer. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on #1 MyRustServer?
The game generates the procedural map on #1 MyRustServer at size 3,000 with seed 356927352. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How do you get onto #1 MyRustServer?
To connect, start Rust, press F1, and type client.connect 185.241.225.51:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167058
BuildBuild number: 167058.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Even marks across the subjects, from F to F.