Working its way up from the back of the class: #15,240 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
52/ 100
D
Moving up: up 609 places this week.
A term to build on.
Strongest in momentum (D); standing 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 70% 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·W··
·······
·······
······W
·······
·······
···
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 gap12.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sun 11 OctFri 18 SepWed 16 Sep
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
Sun 11 Oct, 22:02 UTC16d ago
0
–
running
0
Fri 18 Sep, 21:12 UTC39d ago
0
–
23 days
0
Wed 16 Sep, 15:57 UTC42d ago
0
–
2.2 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 reports the location a server gives; it does not check where the machine actually is. You can connect at 83.143.157.196:28015.
How reliable is nameserver, and is it up?
At this moment, nameserver is offline; the last time it was seen was 11 days 9 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 14 September 2026.
What Rust version is nameserver on?
Rust network protocol 2634 and build 167398 on Windows is what nameserver runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does nameserver reset?
nameserver wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 16 days 22 hours have passed since this world was made.
What happens on nameserver when wipe day arrives?
Recent wipes have peaked at 0 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does nameserver sit among Rust servers?
Over the last seven days, nameserver has #15,240 for player hours, in the top 70% of all ranked servers.
How many players does nameserver usually have?
It has been 11 days 9 hours since nameserver was last seen, and it is offline right now.
Tags and filters
How should you read the tags on nameserver?
You'll see nameserver tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): Build number: 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does nameserver appear in the Rust Server Score lists and filters?
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.
Server rules
What settings and rules apply on nameserver?
The name of nameserver gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on nameserver?
nameserver runs a procedural map, which the game generates.
Getting in
What is the way to join nameserver?
To connect, start Rust, press F1, and type client.connect 83.143.157.196:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersThe server holds 5 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildBuild number: 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
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. Strongest in momentum (D); standing is the one to work on (F).