Rust Data

rustdata.spaceservers79.140.243.76:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 79.140.243.76:28015 checked 9d ago

Ямало-Ненецкий 2x No limit|TP|Home|Kits

2x monthly wipes moddedoxide

Connect

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

Right now

srv.summary()
players now 0/51 # 0% full
7-day average 0 # peak –
rank #15,132 # top 69%
last wipe 9d ago # monthly schedule
next wipe 6d 21h # Thu 5 Nov, 19:00 UTC FW

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. 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
15k10k15k20k10 Oct13 Oct16 Oct21 Oct24 Oct27 Oct

Top 69% 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 6d 21h. # The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

inatkind
06d 21hThu 5 Nov, 19:00 UTCFW force wipe
134d 21hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 04:12 UTC9d ago 1 NaN running 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
79.140.243.76:28015
region
–
max players
51
group limit
8, the default
wipe schedule
monthly
last wipe
20 Oct 2026, 04:12 UTC
hostname
–
first seen
10 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 815 on average520/600
1Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 614 on average1196/1275
2EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 351 on average636/700
3Vitality - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 297 on average725/850
4EU Limitless 2x Monthly Main | No BP Wipes | x2EU · groups of 12+ · 2x · monthly · 277 on average244/260
5MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 141 on average57/500

Quick answers

From the figures on this page.

Population data

How does Ямало-Ненецкий 2x No limit|TP|Home|Kits compare in the rankings?

Player hours over seven days put Ямало-Ненецкий 2x No limit|TP|Home|Kits at #15,132, in the top 69% of the ranked set.

What population does Ямало-Ненецкий 2x No limit|TP|Home|Kits carry?

The current row shows Ямало-Ненецкий 2x No limit|TP|Home|Kits offline; the last response was 9 days 8 hours ago.

About the server

Which Rust version is Ямало-Ненецкий 2x No limit|TP|Home|Kits on?

Version Rust network protocol 2634 and build 167781 on Windows is reported by Ямало-Ненецкий 2x No limit|TP|Home|Kits. The protocol has to match before you can join, and Steam does the updating.

How reliable is Ямало-Ненецкий 2x No limit|TP|Home|Kits, and is it up?

Offline now for Ямало-Ненецкий 2x No limit|TP|Home|Kits, last seen 9 days 8 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 10 October 2026.

In which location is Ямало-Ненецкий 2x No limit|TP|Home|Kits hosted?

The name of Ямало-Ненецкий 2x No limit|TP|Home|Kits points to Europe, even though no region tag is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 79.140.243.76:28015.

Map and rules

Which settings and rules does Ямало-Ненецкий 2x No limit|TP|Home|Kits run?

2x gather is what the name states, and the name is Ямало-Ненецкий 2x No limit|TP|Home|Kits. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on Ямало-Ненецкий 2x No limit|TP|Home|Kits?

Ямало-Ненецкий 2x No limit|TP|Home|Kits runs a procedural map, which the game generates.

Wipes and dates

When does Ямало-Ненецкий 2x No limit|TP|Home|Kits wipe, and on what schedule?

The only wipe Ямало-Ненецкий 2x No limit|TP|Home|Kits takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 9 days 17 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.

On Ямало-Ненецкий 2x No limit|TP|Home|Kits, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 9 hours in.

Tags and filters

Where does Ямало-Ненецкий 2x No limit|TP|Home|Kits appear among Rust Data lists and filters?

These Rust Data lists include Ямало-Ненецкий 2x No limit|TP|Home|Kits: EU Rust servers, Modded Rust servers and 2x Rust servers. Under these filters on the server list, it is listed: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks; Gather rate: 2x.

Which meanings do the tags on Ямало-Ненецкий 2x No limit|TP|Home|Kits hold?

These tags are published by Ямало-Ненецкий 2x No limit|TP|Home|Kits and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp51 (Max players): 51 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

What is the way to join Ямало-Ненецкий 2x No limit|TP|Home|Kits?

The manual route: launch Rust, F1, then client.connect 79.140.243.76:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp51
Max players 51 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Wipe schedule

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

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 84,577 players 11,817 servers online