Offline 79.140.243.71:28015 checked 8h ago
Ямало-Ненецкий 2x No limit|TP|Home|Kits
Connect
srv = rust.server("79.140.243.71: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. 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 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 20h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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.71:28015
- region
- –
- max players
- 51
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 25 Oct 2026, 07:16 UTC
- hostname
- ^
- first seen
- 27 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 · 710 on average | 590/650 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 532 on average | 404/425 |
| 2 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 319 on average | 213/230 |
| 3 | Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 294 on average | 94/150 |
| 4 | EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 257 on average | 272/275 |
| 5 | MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 | EU · groups of 300+ · 2x · monthly · 157 on average | 86/500 |
Quick answers
From the figures on this page.
Population data
What position does Ямало-Ненецкий 2x No limit|TP|Home|Kits take in the server rankings?
Over the last seven days Ямало-Ненецкий 2x No limit|TP|Home|Kits sits at #12,773 on player hours, in the top 58% of ranked servers.
How many players does Ямало-Ненецкий 2x No limit|TP|Home|Kits hold at once?
Ямало-Ненецкий 2x No limit|TP|Home|Kits returns no live count at this refresh, having last been seen 8 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 14:00 UTC is the busiest, at 1 players.
Server data
What does performance look like on Ямало-Ненецкий 2x No limit|TP|Home|Kits?
The 48-hour average is 86 server fps, with a low of 86. Buildings, deployables and all else in the world took the count as high as 69,578 entities. The memory field tops out at 1,986 MB. What players call lag is these two fields together: low fps and a rising entity count.
Which Rust version is Ямало-Ненецкий 2x No limit|TP|Home|Kits on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Ямало-Ненецкий 2x No limit|TP|Home|Kits. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Ямало-Ненецкий 2x No limit|TP|Home|Kits, and is it online now?
Ямало-Ненецкий 2x No limit|TP|Home|Kits is offline at this refresh; the last response came 8 hours ago. Count back 34 minutes from its reported uptime to get the last restart. Rust Data logged it first on 27 October 2026.
In which location is Ямало-Ненецкий 2x No limit|TP|Home|Kits hosted?
Its name points to Europe, but Ямало-Ненецкий 2x No limit|TP|Home|Kits publishes no region tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 79.140.243.71:28015 is its address.
Rules, settings, map
Which settings and rules does Ямало-Ненецкий 2x No limit|TP|Home|Kits run?
The name carries the figure: Ямало-Ненецкий 2x No limit|TP|Home|Kits runs 2x gather. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has Ямало-Ненецкий 2x No limit|TP|Home|Kits selected?
Ямало-Ненецкий 2x No limit|TP|Home|Kits runs a procedural map of size 3,500 with seed 1862422565, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does Ямало-Ненецкий 2x No limit|TP|Home|Kits wipe, and on what schedule?
An estimate from the force wipe gives Ямало-Ненецкий 2x No limit|TP|Home|Kits's next wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 2 days 15 hours ago. A monthly wipe schedule is published in its tags.
Tags and filters
Which Rust Data filters and lists contain Ямало-Ненецкий 2x No limit|TP|Home|Kits?
The Rust Data lists that Ямало-Ненецкий 2x No limit|TP|Home|Kits fits are: EU Rust servers, Modded Rust servers and 2x Rust servers. These filters bring it up 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 3 days; Gather rate: 2x.
How should you read the server tags on Ямало-Ненецкий 2x No limit|TP|Home|Kits?
Read by the game's server browser, the tags Ямало-Ненецкий 2x No limit|TP|Home|Kits publishes are: gmrust (Game mode): Rust survival in its standard form; mp51 (Max players): Slot count: 51; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; modded (Modded): The Modded section lists it, because plugins or settings change the game. 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
How can I connect to Ямало-Ненецкий 2x No limit|TP|Home|Kits?
The manual route: launch Rust, F1, then client.connect 79.140.243.71:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://discord.com/invite/Hnv6CHyh3.