#1 YamitoriTown | Moscow | RU | Modded x2
Offline 79.127.206.186:28015 checked 42d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestWipe schedule
from the wipes we sawNext wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 841 on average | 774 / 800 |
| Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 617 on average | 455 / 475 |
| EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 350 on average | 665 / 685 |
| Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 303 on average | 141 / 150 |
| EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 284 on average | 336 / 340 |
| MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 | EU · groups of 300+ · 2x · monthly · 144 on average | 134 / 500 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for #1 YamitoriTown | Moscow | RU | Modded x2: what is it?
The estimate for #1 YamitoriTown | Moscow | RU | Modded x2's next wipe comes from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world now in play was created 42 days 19 hours ago. A monthly wipe schedule is published in its tags.
Server details
Which location hosts #1 YamitoriTown | Moscow | RU | Modded x2?
The name of #1 YamitoriTown | Moscow | RU | Modded x2 points to Europe, though no region tag is published. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 79.127.206.186:28015.
Which Rust version is #1 YamitoriTown | Moscow | RU | Modded x2 on?
Rust network protocol 2633 and build 163794 on Windows is the setup for #1 YamitoriTown | Moscow | RU | Modded x2. Joining requires the same protocol on your game; Steam handles the update.
Is #1 YamitoriTown | Moscow | RU | Modded x2 up, and how steady is its uptime?
Offline at this refresh: #1 YamitoriTown | Moscow | RU | Modded x2, last seen 42 days 18 hours ago. Of 168 hours in the last 7 full days, 0 were up: 0%. The first sighting of it by Rust Server Analytics was on 16 September 2026.
Tags
How should the tags on #1 YamitoriTown | Moscow | RU | Modded x2 be read?
gmrust (Game mode): Rust survival, standard ruleset; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default team size of 8; v2633 (Protocol): Protocol 2633 is required: your game must match to connect; cs163794 (Build): Build number 163794; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^m (Monthly): A monthly cycle, with Facepunch's force wipe as the reset; ^z (Modded): Plugins or settings change the game, so it sits under Modded; ^y (Carbon): It runs Carbon for plugins are the tags #1 YamitoriTown | Moscow | RU | Modded x2 publishes, and the game's server browser reads them. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
On Rust Server Analytics, which lists and filters feature #1 YamitoriTown | Moscow | RU | Modded x2?
These Rust Server Analytics lists include #1 YamitoriTown | Moscow | RU | Modded x2: Rust servers with a 2x gather rate, EU Rust servers: live population data and Modded Rust servers: live data. It appears on the server list under the following filters: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Population
Where does #1 YamitoriTown | Moscow | RU | Modded x2 sit among Rust servers?
On player hours over seven days, #1 YamitoriTown | Moscow | RU | Modded x2 ranks #15,519, within the top – of ranked servers.
What is the population of #1 YamitoriTown | Moscow | RU | Modded x2?
The last sighting of #1 YamitoriTown | Moscow | RU | Modded x2 was 42 days 18 hours ago; it is offline at this refresh.
Settings
What are the settings on #1 YamitoriTown | Moscow | RU | Modded x2, and its rules?
2x gathering is what #1 YamitoriTown | Moscow | RU | Modded x2 states in its name. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Carbon are in use. The server runs with VAC, Valve's anti-cheat, enabled.
The map on #1 YamitoriTown | Moscow | RU | Modded x2: which one is it?
The game generates a procedural map for #1 YamitoriTown | Moscow | RU | Modded x2.
Connection
How do you connect to #1 YamitoriTown | Moscow | RU | Modded x2?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 79.127.206.186:28015.