Working its way up from the back of the class: #13,027 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
45/ 100
D
Slipped a little: down 1,288 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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 59% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
···
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 gap1 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Fri 16 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 46 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 16:29 UTC12d ago
1
–
running
1
Thu 15 Oct, 16:39 UTC13d ago
1
–
1 days
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
You'll find no region listed by #1 MyRustServer. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 86.22.138.188:28015.
How reliable is #1 MyRustServer, and is it up?
You cannot join now: #1 MyRustServer is offline, last seen 10 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 8 October 2026.
Which Rust version is #1 MyRustServer running?
Rust network protocol 2634 and build 167781 on Windows is what #1 MyRustServer runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does #1 MyRustServer wipe its map?
There are too few wipes on record for #1 MyRustServer to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 12 days 4 hours.
What happens on #1 MyRustServer when wipe day arrives?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 46 hours after it began.
Player numbers
Where does #1 MyRustServer sit among Rust servers?
Over the last seven days, #1 MyRustServer has #13,027 for player hours, in the top 59% 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 10 days 5 hours ago.
Tags and filters
What is meant by the tags on #1 MyRustServer?
The game's browser takes its cue from the tags #1 MyRustServer has set: gmrust (Game mode): Rust survival, played by the standard rules; 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): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
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; Last wipe: In the last 2 weeks.
Map and rules
How is #1 MyRustServer set up, and what rules does it keep?
Nothing in the name of #1 MyRustServer 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. 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.
Which map is in play on #1 MyRustServer?
A procedural map, generated by the game, is what #1 MyRustServer runs.
Connecting
How should you connect to #1 MyRustServer?
Enter client.connect 86.22.138.188: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 asmp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 D.