Working its way up from the back of the class: #13,839 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
30/ 100
F
Lost ground: down 5,427 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.
AveragePeak
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
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 gap0.8 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sat 3 OctFri 2 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
Sat 3 Oct, 13:42 UTC25d ago
1
–
running
0
Fri 2 Oct, 18:01 UTC26d ago
1
–
0.8 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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 31.76.249.114:28015.
How reliable is nameserver, and is it up?
You cannot join now: nameserver is offline, last seen 24 days 4 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 24 September 2026.
What Rust version is nameserver on?
Rust network protocol 2634 and build 166586 on Windows is what nameserver runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does nameserver wipe, and how often?
The record holds too few of nameserver'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. It has been running its current world for 25 days 5 hours.
What happens on nameserver when wipe day arrives?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does nameserver place in the wider field of Rust servers?
Over the last seven days, nameserver has #13,839 for player hours, in the top 61% of all ranked servers.
How many players does nameserver usually have?
The last sighting of nameserver was 24 days 4 hours ago, and it is offline right now.
Tags and filters
What do nameserver's tags stand for?
The game's browser takes its cue from the tags nameserver has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; 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; cs166586 (Build): Build number: 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 lists and filters on Rust Server Score show nameserver?
Rust Server Score lists that include nameserver: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on nameserver?
Nothing in the name of nameserver states a gather rate. 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. The plugin count runs to Oxide. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map nameserver uses?
nameserver runs a procedural map, which the game generates.
Getting in
How should you connect to nameserver?
To connect, start Rust, press F1, and type client.connect 31.76.249.114:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
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.
cs166586
BuildBuild number: 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: 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.