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 13h. 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. The world you are playing on was built 42 days 9 hours. Its tags give wipes as monthly.
These are the Rust Live Stats lists #1 YamitoriTown | Moscow | RU | Modded x2 fits: 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): 50 slots are available; ts8 (Group limit): 8 per team at most, the game's default setting; v2633 (Protocol): Join only if your game is on protocol 2633; cs163794 (Build): This server runs game build 163794; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): Region code: none set; ^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. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
#1 YamitoriTown | Moscow | RU | Modded x2 is not online at the moment, having last been seen 42 days 7 hours ago.
Ranked by seven-day player hours, #1 YamitoriTown | Moscow | RU | Modded x2 is #15,514, placing it in the top – of ranked servers.
Gather rates on #1 YamitoriTown | Moscow | RU | Modded x2 are 2x, as its name states. The default applies: 8 players to a group. It runs survival, the standard game: gather, build, raid. You can raid and fight other players. Plugins or settings change the game, and the browser lists it as Modded. The plugin load is Carbon. Anti-cheat: VAC from Valve is enabled.
A procedural map, generated by the game, runs on #1 YamitoriTown | Moscow | RU | Modded x2.
No region tag is published, though the name of #1 YamitoriTown | Moscow | RU | Modded x2 points to Europe. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 95.73.121.253:28015 is its address.
Rust network protocol 2633 and build 163794 on Windows is what #1 YamitoriTown | Moscow | RU | Modded x2 runs. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, #1 YamitoriTown | Moscow | RU | Modded x2 is down, last seen 42 days 7 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. Rust Live Stats has tracked it since 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 95.73.121.253:28015.