Working its way up from the back of the class: #15,891 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,788 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.
No daily history yet.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 9 Oct. 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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
The name of Ямало-Ненецкий points to Europe, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 79.140.243.166:28015.
How reliable is Ямало-Ненецкий, and is it up?
You cannot join now: Ямало-Ненецкий is offline, last seen 19 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 9 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Ямало-Ненецкий sit?
Rust network protocol 2634 and build 167231 on Windows is what Ямало-Ненецкий runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Ямало-Ненецкий wipe its map?
The next wipe on Ямало-Ненецкий is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 20 days 9 hours. Its tags list a monthly wipe schedule.
Population
Where does Ямало-Ненецкий sit among Rust servers?
Over the last seven days, Ямало-Ненецкий has #15,891 for player hours, in the top 72% of all ranked servers.
How many players does Ямало-Ненецкий usually have?
The last sighting of Ямало-Ненецкий was 19 days 11 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on Ямало-Ненецкий?
You'll see Ямало-Ненецкий tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp51 (Max players): 51 slots are available; 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; cs167231 (Build): The game build is 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under 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.
Which Rust Server Score filters and lists feature Ямало-Ненецкий?
Rust Server Score lists that include Ямало-Ненецкий: European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
How is Ямало-Ненецкий set up, and what rules does it keep?
You will find no gather rate in the name of Ямало-Ненецкий. The group limit stays at the game's default of 8 players. survival is the mode 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Ямало-Ненецкий runs which map?
The game generates the procedural map on Ямало-Ненецкий at size 3,700 with seed 1034224783. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto Ямало-Ненецкий?
To connect, start Rust, press F1, and type client.connect 79.140.243.166:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/GuvFZyYwM.
Server tags
what each one means
Published asmp51,ptrak,$r?,v2634,^m,gmrust,cs167231,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp51
Max players51 slots are available.
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.
cs167231
BuildThe game build is 167231.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.