Offline 79.140.243.57:28015 checked 8d ago
Ямало-Ненецкий 2x No limit|TP|Home|Kits
Connect
srv = rust.server("79.140.243.57:28016")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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 17 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 bestTop 70% 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 7d 18h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 18h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 18h | Thu 3 Dec, 19:00 UTC | FW 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 | Tue 20 Oct, 04:12 UTC8d 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
3500 · seed 1862422565
- map
- Procedural Map
- size
- 3500
- seed
- 1862422565
Server
srv.info()- address
- 79.140.243.57:28015
- region
- –
- max players
- 51
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 20 Oct 2026, 04:12 UTC
- hostname
- ^
- first seen
- 17 Oct 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 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 798 on average | 404/450 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 595 on average | 197/225 |
| 2 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 348 on average | 91/150 |
| 3 | Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 302 on average | 45/50 |
| 4 | EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 276 on average | 165/200 |
| 5 | MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 | EU · groups of 300+ · 2x · monthly · 150 on average | 44/500 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Ямало-Ненецкий 2x No limit|TP|Home|Kits rank?
Over the last seven days Ямало-Ненецкий 2x No limit|TP|Home|Kits sits at #15,346 on player hours, in the top 70% of ranked servers.
How full does Ямало-Ненецкий 2x No limit|TP|Home|Kits run?
Ямало-Ненецкий 2x No limit|TP|Home|Kits returns no live count at this refresh, having last been seen 8 days 16 hours ago.
Server facts
What is the Rust version on Ямало-Ненецкий 2x No limit|TP|Home|Kits?
The build is Rust network protocol 2634 and build 167781 on Windows, run by Ямало-Ненецкий 2x No limit|TP|Home|Kits. Steam updates your game for you, but the protocol must match to join.
Is Ямало-Ненецкий 2x No limit|TP|Home|Kits up, and what does its uptime show?
Ямало-Ненецкий 2x No limit|TP|Home|Kits is offline at this refresh; the last response came 8 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 17 October 2026.
Which location does Ямало-Ненецкий 2x No limit|TP|Home|Kits run from?
No region tag is published by Ямало-Ненецкий 2x No limit|TP|Home|Kits, though its name points to Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 79.140.243.57:28015 is its address.
Map and rules
What rules and settings are recorded for Ямало-Ненецкий 2x No limit|TP|Home|Kits?
Gather sits at 2x, read from the server's own name: Ямало-Ненецкий 2x No limit|TP|Home|Kits. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Ямало-Ненецкий 2x No limit|TP|Home|Kits loaded?
The game generates the map on Ямало-Ненецкий 2x No limit|TP|Home|Kits: procedural, size 3,500, seed 1862422565. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does Ямало-Ненецкий 2x No limit|TP|Home|Kits wipe, and how often?
Once a month Ямало-Ненецкий 2x No limit|TP|Home|Kits wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 8 days 20 hours ago. 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 0 hours in.
Tags and filters
Which Rust Data filters and lists contain Ямало-Ненецкий 2x No limit|TP|Home|Kits?
These Rust Data lists include Ямало-Ненецкий 2x No limit|TP|Home|Kits: EU Rust servers, Modded Rust servers and 2x 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; Last wipe: In the last 2 weeks; Gather rate: 2x.
Which meanings do the tags on Ямало-Ненецкий 2x No limit|TP|Home|Kits hold?
Read by the game's server browser, the tags Ямало-Ненецкий 2x No limit|TP|Home|Kits publishes are: gmrust (Game mode): Survival play, standard Rust; mp51 (Max players): 51 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Ямало-Ненецкий 2x No limit|TP|Home|Kits?
In Rust, F1 opens the console: type client.connect 79.140.243.57:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.