Rust Data

rustdata.spaceservers79.140.252.67:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 79.140.252.67:28015 checked 20d ago

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

monthly wipes moddedoxide

Connect

srv = rust.server("79.140.252.67:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/51 # 0% full
7-day average 0 # peak –
rank #13,417 # top 60%
last wipe 20d ago # monthly schedule
next wipe 8d 13h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k4 Oct6 Oct8 Oct10 Oct12 Oct14 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 8d 13h. # The force wipe · high confidence

usual gap0.4 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes

Coming wipes

inatkind
08d 13hThu 5 Nov, 19:00 UTCFW force wipe
136d 13hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Wed 7 OctWed 7 OctTue 6 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 7 Oct, 09:29 UTC20d ago 2 NaN running 1
1 Wed 7 Oct, 02:16 UTC21d ago 2 NaN 0.3 days 1
2 Tue 6 Oct, 15:41 UTC21d ago 2 NaN 0.4 days 1
3 Mon 5 Oct, 09:47 UTC22d ago 1 NaN 1.2 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.

display(srv.map, srv.info())

Map

3700 · seed 1034224783
Map of Ямало-Ненецкий
map
Procedural Map
size
3700
seed
1034224783
Open on RustMaps

Server

srv.info()
address
79.140.252.67:28015
region
–
max players
51
group limit
8, the default
wipe schedule
monthly
last wipe
7 Oct 2026, 11:15 UTC
hostname
^
first seen
4 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average28/700
1404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average12/1000
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10EU · groups of 16+ · monthly · 67 on average8/1000
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10EU · groups of 16+ · monthly · 61 on average48/1000
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 59 on average79/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 21.10EU · groups of 16+ · monthly · 58 on average0/1000

Quick answers

From the figures on this page.

Population

What position does Ямало-Ненецкий take in the server rankings?

Rank #13,417 on seven-day player hours for Ямало-Ненецкий, within the top 60% of all ranked servers.

How full does Ямало-Ненецкий run?

Ямало-Ненецкий returns no live count at this refresh, having last been seen 20 days 14 hours ago.

Server data

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

Version Rust network protocol 2634 and build 167058 on Windows is reported by Ямало-Ненецкий. Joining needs the same protocol on your game; Steam handles the update.

Is Ямало-Ненецкий up, and what does its uptime show?

The latest sample has Ямало-Ненецкий offline, with a last sighting 20 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 4 October 2026.

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

Its name points to Europe, but Ямало-Ненецкий publishes no region tag. Rust Data does not look up where the machine stands; it shows where a server says it is. 79.140.252.67:28015 is its address.

Map and rules

What rules and settings are recorded for Ямало-Ненецкий?

You will not find a gather rate in the string Ямало-Ненецкий. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

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

The game generates the map on Ямало-Ненецкий: procedural, size 3,700, seed 1034224783. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

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

Once a month Ямало-Ненецкий wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 20 days 18 hours ago. Its tags carry a monthly wipe schedule.

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

Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 2 hours after it began.

Tags, lists

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

These Rust Data lists include Ямало-Ненецкий: EU Rust servers and Modded Rust servers. It appears under these 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.

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

The game's server browser reads these tags from Ямало-Ненецкий: gmrust (Game mode): Survival play, standard Rust; mp51 (Max players): Slot count: 51; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167058 (Build): The server runs build 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join Ямало-Ненецкий?

Enter client.connect 79.140.252.67:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/GuvFZyYwM is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp51,ptrak,$r?,v2634,^m,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp51
Max players Slot count: 51.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol To join, your game must run protocol 2634.
cs167058
Build The server runs build 167058.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Wipe schedule

^m
Monthly Monthly: the wipe lands with Facepunch's force wipe.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the 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.

Rust Data 33,127 players 11,603 servers online