RUST METRICSFlight deck · live data
Data live Servers11,617 Players34,993 Populated2,836 Fresh wipes 3 h74 Scan5 min
‹ All servers79.140.252.222:52206
Offline Full Queue Fresh wipe Wipe due No query

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

Offline 79.140.252.222:52206 checked 31d 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#14,550top 61%
Last wipe31d 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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 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

What wipe timing does Ямало-Ненецкий follow?

Its rhythm cannot be told from the wipes of Ямало-Ненецкий on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 31 days 19 hours ago the current world was made.

Tag meanings

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

These are the tags Ямало-Ненецкий publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp41 (Max players): Slots: 41; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. 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?

On Rust Metrics, Ямало-Ненецкий sits in these lists: EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

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

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

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

Ямало-Ненецкий is not responding; status offline, last seen 31 days 17 hours ago.

Operator and location

Which location does Ямало-Ненецкий run from?

Reading: location. Nothing in the tags, but the name of Ямало-Ненецкий points to Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 79.140.252.222:52206.

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

Rust network protocol 2633 and build 164530 on Windows is the build Ямало-Ненецкий runs. Matching protocol is required to join. Let Steam update your game.

Is Ямало-Ненецкий up, and how often does it stay up?

Reading: offline. Ямало-Ненецкий last answered 31 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 27 September 2026.

Settings and map

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

Reading the name gives no gather rate for Ямало-Ненецкий. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

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

From seed 1234, the game generates the procedural map on Ямало-Ненецкий. Its size is 3,500. 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 Ямало-Ненецкий?

To join: start Rust, press F1 and type client.connect 79.140.252.222:52206. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp41,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp41
Max players Slots: 41.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build The server runs game build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.