Working its way up from the back of the class: #15,837 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
31/ 100
F
Lost ground: down 5,940 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.
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.
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 8 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 8d 16h.
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. You can connect at 79.140.252.150:28015.
Is Ямало-Ненецкий up, and how steady is its uptime?
The server is down: Ямало-Ненецкий is offline now, with the last sighting 18 days 22 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 8 October 2026.
Which Rust version is Ямало-Ненецкий running?
Rust network protocol 2634 and build 167231 on Windows is what Ямало-Ненецкий runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Ямало-Ненецкий reset?
The estimate for Ямало-Ненецкий's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 19 days 15 hours. Its tags list a monthly wipe schedule.
Player count
What position does Ямало-Ненецкий hold in the rankings?
In the top 72% of all ranked servers, Ямало-Ненецкий sits at #15,837 for player hours over the last seven days.
Is Ямало-Ненецкий a busy server?
Ямало-Ненецкий is offline at the moment; the last time it was seen was 18 days 22 hours ago.
Lists and filters
What is meant by the tags on Ямало-Ненецкий?
You'll see Ямало-Ненецкий tagged with gmrust (Game mode): Survival in the standard Rust style; mp51 (Max players): 51 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; cs167231 (Build): This runs on build 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Ямало-Ненецкий appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Ямало-Ненецкий among them: 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.
Rules and settings
Which rules does Ямало-Ненецкий enforce, and what are its settings?
You will find no gather rate in the name of Ямало-Ненецкий. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Ямало-Ненецкий runs which map?
A procedural map of size 3,700 and seed 1034224783, generated by the game, is what Ямало-Ненецкий runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to Ямало-Ненецкий?
To connect, start Rust, press F1, and type client.connect 79.140.252.150:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at 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 modeSurvival in the standard Rust style.
mp51
Max players51 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.
cs167231
BuildThis runs on build 167231.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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.