Working its way up from the back of the class: #13,819 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
34/ 100
F
Lost ground: down 4,510 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
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·WW·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 gap1.7 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Fri 2 OctWed 30 SepTue 29 Sep
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
Fri 2 Oct, 03:05 UTC27d ago
1
–
running
1
Wed 30 Sep, 09:19 UTC29d ago
1
–
1.7 days
0
Tue 29 Sep, 05:05 UTC30d ago
1
–
1.2 days
0
Sun 27 Sep, 11:27 UTC32d ago
1
–
1.7 days
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
No region tag appears for Ямало-Ненецкий, but the name suggests Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 79.140.252.222:28015.
How reliable is Ямало-Ненецкий, and is it up?
You cannot join now: Ямало-Ненецкий is offline, last seen 27 days 17 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 25 September 2026, Rust Server Score saw it for the first time.
What Rust version is Ямало-Ненецкий on?
The server Ямало-Ненецкий is on Rust network protocol 2634 and build 166494 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Ямало-Ненецкий wipe, and how often?
There is no next wipe to predict on Ямало-Ненецкий, as it wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 27 days 20 hours have passed since this world was made.
What should you expect from wipe day on Ямало-Ненецкий?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
Where does Ямало-Ненецкий sit among Rust servers?
Over the last seven days, Ямало-Ненецкий has #13,819 for player hours, in the top 60% of all ranked servers.
How many players does Ямало-Ненецкий usually have?
It has been 27 days 17 hours since Ямало-Ненецкий was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Ямало-Ненецкий?
gmrust (Game mode): Survival in the standard Rust style; mp41 (Max players): The server holds 41 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Ямало-Ненецкий publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
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. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does Ямало-Ненецкий enforce, and what are its settings?
You will find no gather rate in the name of Ямало-Ненецкий. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Ямало-Ненецкий?
A procedural map of size 3,750 and seed 12345, generated by the game, is what Ямало-Ненецкий runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to Ямало-Ненецкий?
To connect, start Rust, press F1, and type client.connect 79.140.252.222:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp41,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp41
Max playersThe server holds 41 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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.