Ямало-Ненецкий 2x No limit|TP|Home|Kits
Offline 79.140.243.76:28015 checked 7d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 9d 0h.
The force wipe · high confidenceComing wipes
- 9d 0hThu 5 Nov, 19:00 UTC19:00 UKFW
- 37d 0hThu 3 Dec, 19:00 UTC19:00 UKFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 9 hours in.
Wipes
every wipe as a delivery, newest first-
Thu 5 Nov, 19:00 UTC FW19:00 UK · in 9d 0hNext wipe expected · the force wipe
-
Tue 20 Oct, 04:12 UTC 05:12 UK · 7d agoWipe delivered
- Peak
- 1
- Crowd
- –
- Lasted
- running
- Players before
- 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes 964 / 1050
- Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes 756 / 825
- EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr 435 / 440
- Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes 202 / 250
- EU Limitless 2x Monthly Main | No BP Wipes | x2 380 / 365
- MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 180 / 500
Quick answers
From the figures on this page.
Player activity
Where does Ямало-Ненецкий 2x No limit|TP|Home|Kits place among Rust servers?
A seven-day player-hours count places Ямало-Ненецкий 2x No limit|TP|Home|Kits at #15,132: the top 69% of every ranked server.
How many players are on Ямало-Ненецкий 2x No limit|TP|Home|Kits right now?
The last sighting of Ямало-Ненецкий 2x No limit|TP|Home|Kits was 7 days 4 hours ago; it is offline right now. Averaged over the past week: 0 players, peaking at 1.
Rules and settings
Which map is active on Ямало-Ненецкий 2x No limit|TP|Home|Kits?
The map on Ямало-Ненецкий 2x No limit|TP|Home|Kits is procedural, produced by the game.
What settings and rules should you know for Ямало-Ненецкий 2x No limit|TP|Home|Kits?
The name of Ямало-Ненецкий 2x No limit|TP|Home|Kits announces 2x gathering. The game's default applies: 8 players to a group at most. You get survival here, the usual game: build, gather, raid. Fighting and raiding between players is allowed. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
About the server
In which region is Ямало-Ненецкий 2x No limit|TP|Home|Kits based?
No region tag comes from Ямало-Ненецкий 2x No limit|TP|Home|Kits, but the name points to Europe. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 79.140.243.76:28015.
Is Ямало-Ненецкий 2x No limit|TP|Home|Kits up, and how good is its uptime?
Ямало-Ненецкий 2x No limit|TP|Home|Kits is offline at the moment, with the last sighting 7 days 4 hours ago. It was up 1 of 168 hours over the last 7 full days, 1% of the time. The first sighting of it by Rust Wipe Tracker came on 10 October 2026.
What Rust version is Ямало-Ненецкий 2x No limit|TP|Home|Kits using?
On Windows, Ямало-Ненецкий 2x No limit|TP|Home|Kits runs Rust network protocol 2634 and build 167781. The same protocol is required to join, and Steam takes care of updating it.
Wipe schedule
How does Ямало-Ненецкий 2x No limit|TP|Home|Kits handle its wipe days?
The average busiest point of its recent wipes was 1 players. 9 hours after the latest wipe, the crowd reached its peak.
On what schedule does Ямало-Ненецкий 2x No limit|TP|Home|Kits reset its map?
Ямало-Ненецкий 2x No limit|TP|Home|Kits wipes with the force wipe and at no other time, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world it is running was made 7 days 14 hours. In its tags it publishes the wipe schedule: monthly.
Tags and listings
On Rust Wipe Tracker, which lists and filters is Ямало-Ненецкий 2x No limit|TP|Home|Kits part of?
These Rust Wipe Tracker lists take Ямало-Ненецкий 2x No limit|TP|Home|Kits: Rust servers with a 2x gather rate, Rust servers in Europe and Modded Rust servers. You will find it 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.
How should you read the tags on Ямало-Ненецкий 2x No limit|TP|Home|Kits?
Read off the game's server browser, the tags for Ямало-Ненецкий 2x No limit|TP|Home|Kits are: gmrust (Game mode): Standard Rust survival is the game mode here; mp51 (Max players): It holds 51 slots; ts8 (Group limit): 8 per team, which is the default; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset; ^m (Monthly): It wipes monthly, together with the force wipe from Facepunch; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.
How to join
What is the process to join Ямало-Ненецкий 2x No limit|TP|Home|Kits?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 79.140.243.76:28015.