RUST METRICSFlight deck · live data
Data live Servers11,637 Players32,508 Populated2,805 Fresh wipes 3 h70 Scan5 min
‹ All servers79.140.243.191:28015
Offline Full Queue Fresh wipe Wipe due No query

Ямало-Ненецкий

Offline 79.140.243.191:28015 checked 25d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 31 41 PAX 1 /41

Players now

2% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,860top 61%
Last wipe25d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct4 Oct6 Oct7 Oct9 Oct10 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

How often does Ямало-Ненецкий wipe, and when?

The rhythm of Ямало-Ненецкий's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 25 days 23 hours ago.

Lists and filters

How should you read the tags on Ямало-Ненецкий?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp41 (Max players): 41 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from Ямало-Ненецкий. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Ямало-Ненецкий appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Ямало-Ненецкий: EU Rust servers, checked and Modded Rust servers, checked live. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does Ямало-Ненецкий hold among Rust servers?

Player hours over seven days put Ямало-Ненецкий at #13,860, in the top 61% of all ranked servers.

What is the population on Ямало-Ненецкий?

Status for Ямало-Ненецкий: offline. Last seen 25 days 21 hours ago.

Operator and location

What location is Ямало-Ненецкий hosted in?

Check: location. No region tag comes from Ямало-Ненецкий, but the name points to Europe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 79.140.243.191:28015.

What Rust version is Ямало-Ненецкий on?

Reading: Ямало-Ненецкий, Rust network protocol 2634 and build 166652, Windows. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Ямало-Ненецкий, and is it online now?

Ямало-Ненецкий reports offline. The last reading came 25 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 3 October 2026.

Settings and map

What rules does Ямало-Ненецкий enforce, and what are its settings?

Check: gather rate. The name Ямало-Ненецкий does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is Ямало-Ненецкий on?

Size 3,700 and seed 12345: the game generates the procedural map on Ямало-Ненецкий from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join Ямало-Ненецкий?

Check: join. Open Rust, press F1, then enter client.connect 79.140.243.191:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp41,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp41
Max players 41 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.