Offline 79.140.252.222:28015 checked 27d ago
Ямало-Ненецкий
Connect
srv = rust.server("79.140.252.222:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 03:05 UTC27d ago | 1 | NaN | running | 1 |
| 1 | Wed 30 Sep, 09:19 UTC29d ago | 1 | NaN | 1.7 days | 0 |
| 2 | Tue 29 Sep, 05:05 UTC30d ago | 1 | NaN | 1.2 days | 0 |
| 3 | Sun 27 Sep, 11:27 UTC31d ago | 1 | NaN | 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.
display(srv.map, srv.info())Map
3750 · seed 12345
- map
- Procedural Map
- size
- 3750
- seed
- 12345
Server
srv.info()- address
- 79.140.252.222:28015
- region
- –
- max players
- 41
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 03:05 UTC
- hostname
- –
- first seen
- 25 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 1 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 58/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 6/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 80 on average | 242/700 |
Quick answers
From the figures on this page.
Population data
What position does Ямало-Ненецкий take in the server rankings?
Player hours over seven days put Ямало-Ненецкий at #13,819, in the top 60% of the ranked set.
What population does Ямало-Ненецкий carry?
Offline now for Ямало-Ненецкий, with the last sample 27 days 3 hours ago.
Server facts
Which Rust version is Ямало-Ненецкий on?
Version Rust network protocol 2634 and build 166494 on Windows is reported by Ямало-Ненецкий. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Ямало-Ненецкий, and is it up?
Offline now for Ямало-Ненецкий, last seen 27 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 25 September 2026.
Which location does Ямало-Ненецкий run from?
No region tag is published by Ямало-Ненецкий, though its name points to Europe. Rust Data does not look up where the machine stands; it shows where a server says it is. 79.140.252.222:28015 is its address.
Settings and map
Which settings and rules does Ямало-Ненецкий run?
You will not find a gather rate in the string Ямало-Ненецкий. No custom cap; the default of 8 players per group stands. 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. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Ямало-Ненецкий loaded?
Ямало-Ненецкий runs a procedural map of size 3,750 with seed 12345, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does Ямало-Ненецкий wipe, and how often?
Ямало-Ненецкий wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 6 hours ago.
On Ямало-Ненецкий, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which Rust Data filters and lists contain Ямало-Ненецкий?
The Rust Data lists that Ямало-Ненецкий fits are: EU Rust servers and Modded Rust servers. 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.
Which meanings do the tags on Ямало-Ненецкий hold?
These tags are published by Ямало-Ненецкий and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp41 (Max players): The server lists 41 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166494 (Build): The server runs build 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 into Ямало-Ненецкий?
In Rust, F1 opens the console: type client.connect 79.140.252.222:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.