Live coverage · Rust server
Offline #1 YamitoriTown | Moscow | RU | Modded x2 is not on the server list right now. The figures below are from when it was last seen, 42d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe
This server has not put up a new map since the desk started watching it.
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.
An estimate from the force wipe gives #1 YamitoriTown | Moscow | RU | Modded x2's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. This world dates from 42 days 18 hours. The tags carry a monthly wipe schedule.
The Rust Live Stats lists that include #1 YamitoriTown | Moscow | RU | Modded x2 are 2x Rust servers live now, EU Rust servers, live and Modded Rust servers live now. These filters on the server list bring it up: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
These are the tags #1 YamitoriTown | Moscow | RU | Modded x2 makes public: gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team at most, the game's default setting; v2633 (Protocol): You need protocol 2633 on your game to get in; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^m (Monthly): It wipes with Facepunch's force wipe, once each month; ^z (Modded): Plugins or settings changes put this under Modded; ^y (Carbon): Plugin framework: Carbon. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
Last seen 42 days 17 hours ago, #1 YamitoriTown | Moscow | RU | Modded x2 is offline right now.
Player hours over seven days put #1 YamitoriTown | Moscow | RU | Modded x2 at #15,519, in the top – of all ranked servers.
The name says it: gathering runs at 2x on #1 YamitoriTown | Moscow | RU | Modded x2. Eight players per group, which is the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. Plugins or settings change the game, and the browser lists it as Modded. Plugins run here: Carbon. Anti-cheat: VAC from Valve is enabled.
The map on #1 YamitoriTown | Moscow | RU | Modded x2 is procedural, made by the game itself.
The name points to Europe even though #1 YamitoriTown | Moscow | RU | Modded x2 publishes no region tag. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 79.127.206.186:28015.
The setup on #1 YamitoriTown | Moscow | RU | Modded x2 is Rust network protocol 2633 and build 163794 with Windows. Joining requires the same protocol on your game; Steam takes care of updating it.
#1 YamitoriTown | Moscow | RU | Modded x2 is currently offline, with its last appearance 42 days 17 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. The first sighting by Rust Live Stats was on 16 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 79.127.206.186:28015.