Working its way up from the back of the class: #14,538 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
29/ 100
F
Lost ground: down 5,997 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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 61% 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 peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 22 Sep, 21:39 UTC36d ago
0
–
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
nameserver leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 81.17.18.109:28015.
How dependable is nameserver, and is it online at the moment?
You cannot join now: nameserver is offline, last seen 31 days 6 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 22 September 2026, Rust Server Score saw it for the first time.
On what Rust version does nameserver sit?
Rust network protocol 2633 and build 165217 on Windows is what nameserver runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does nameserver wipe its map?
nameserver has not had enough wipes recorded to reveal 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 36 days 8 hours.
What happens on nameserver when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
What position does nameserver hold in the rankings?
Over the last seven days, nameserver has #14,538 for player hours, in the top 61% of all ranked servers.
How many players does nameserver usually have?
The last sighting of nameserver was 31 days 6 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on nameserver?
gmrust (Game mode): Rust survival, played by the standard rules; mp15 (Max players): Its slot count is 15; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags nameserver publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does nameserver appear in the Rust Server Score lists and filters?
Rust Server Score lists that include nameserver: 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. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map nameserver uses?
nameserver runs a procedural map, which the game generates.
Connecting
What is the way to join nameserver?
Enter client.connect 81.17.18.109: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 asmp15,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp15
Max playersIts slot count is 15.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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 standing (F); momentum is the one to work on (F).