Offline 79.140.252.222:28015 checked 30d ago
Ямало-Ненецкий
Connect
srv = rust.server("79.140.252.222:28018")
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 26 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 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 29 Sep, 05:05 UTC30d ago | 0 | NaN | running | 0 |
| 1 | Mon 28 Sep, 12:10 UTC31d ago | 1 | NaN | 0.7 days | 1 |
| 2 | Mon 28 Sep, 01:44 UTC31d ago | 1 | NaN | 0.4 days | 0 |
| 3 | Sun 27 Sep, 15:17 UTC31d ago | 1 | NaN | 0.4 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
3500 · seed 1234
- map
- Procedural Map
- size
- 3500
- seed
- 1234
Server
srv.info()- address
- 79.140.252.222:28015
- region
- –
- max players
- 41
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 05:05 UTC
- hostname
- –
- first seen
- 26 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 | 128/100 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 83/700 |
| 2 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 23/200 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 28/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 267/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 73 on average | 118/1000 |
Quick answers
From the figures on this page.
Population data
What position does Ямало-Ненецкий take in the server rankings?
Rank #16,905 on seven-day player hours for Ямало-Ненецкий, within the top 71% of all ranked servers.
How full does Ямало-Ненецкий run?
Ямало-Ненецкий returns no live count at this refresh, having last been seen 30 days 8 hours ago.
About the server
What Rust version does Ямало-Ненецкий run?
Rust network protocol 2633 and build 164530 on Windows is what Ямало-Ненецкий runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Ямало-Ненецкий, and is it up?
The latest sample has Ямало-Ненецкий offline, with a last sighting 30 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 26 September 2026.
Where does Ямало-Ненецкий sit?
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.222:28015 is its address.
Map and rules
Which rules apply on Ямало-Ненецкий, and what settings?
No gather rate appears in the name: Ямало-Ненецкий. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Ямало-Ненецкий selected?
The game generates the map on Ямало-Ненецкий: procedural, size 3,500, seed 1234. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Ямало-Ненецкий wipe, and how often?
No next wipe can be predicted for Ямало-Ненецкий, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 30 days 8 hours ago.
What is wipe day on Ямало-Ненецкий like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain Ямало-Ненецкий?
On Rust Data, Ямало-Ненецкий appears in these lists: EU Rust servers and Modded Rust servers. It appears under these filters 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?
The game's server browser reads these tags from Ямало-Ненецкий: gmrust (Game mode): Survival play, standard Rust; mp41 (Max players): The server lists 41 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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 Ямало-Ненецкий?
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.