Working its way up from the back of the class: #15,868 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
35/ 100
F
Slipped a little: down 4,898 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.
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
WW·····
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap0.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Tue 6 OctMon 5 OctSun 4 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 6 Oct, 12:37 UTC21d ago
1
–
running
0
Mon 5 Oct, 12:27 UTC22d ago
1
–
1 days
0
Sun 4 Oct, 19:01 UTC23d ago
1
–
0.7 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
No region is published for nameserver. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 87.250.201.91:28015.
How dependable is nameserver, and is it online at the moment?
The server is down: nameserver is offline now, with the last sighting 18 days 4 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 4 October 2026.
On what Rust version does nameserver sit?
You will find nameserver on Rust network protocol 2634 and build 166652, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does nameserver wipe, and how often?
There is no next wipe to predict on nameserver, as it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 21 days 10 hours have passed since this world was made.
What happens on nameserver when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does nameserver sit among Rust servers?
Over the last seven days, nameserver has #15,868 for player hours, in the top 72% of all ranked servers.
Is nameserver a busy server?
It has been 18 days 4 hours since nameserver was last seen, and it is offline right now.
Tags and filters
How should you read the tags on nameserver?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): 3 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags nameserver publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature nameserver?
These Rust Server Score lists count nameserver 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.
Map and rules
How is nameserver set up, and what rules does it keep?
You will find no gather rate in the name of nameserver. The group limit stays at the game's default of 8 players. It runs survival, 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. VAC, Valve's anti-cheat, is enabled.
Which map is in play on nameserver?
The game generates a procedural map for nameserver.
Getting in
How should you connect to nameserver?
To connect, start Rust, press F1, and type client.connect 87.250.201.91:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max players3 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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.