#1 YamitoriTown | Moscow | RU | Modded x2
Offline 95.73.121.253: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 13h. 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 · 807 on average | 284 / 300 |
| Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 600 on average | 111 / 125 |
| EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 350 on average | 45 / 150 |
| Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 302 on average | 4 / 50 |
| EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 278 on average | 64 / 200 |
| MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 | EU · groups of 300+ · 2x · monthly · 150 on average | 27 / 500 |
Quick answers
from the figures on this pageWipe data
The wipe schedule for #1 YamitoriTown | Moscow | RU | Modded x2: what is it?
An estimate from the force wipe gives #1 YamitoriTown | Moscow | RU | Modded x2's next wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC, the force wipe that reaches every Rust server. The current world dates from 42 days 8 hours. Its tags state a wipe schedule of one month.
Server details
In which region does #1 YamitoriTown | Moscow | RU | Modded x2 sit?
Without a region tag, #1 YamitoriTown | Moscow | RU | Modded x2 still has a name that points to Europe. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 95.73.121.253:28015 is its address.
Which Rust version is #1 YamitoriTown | Moscow | RU | Modded x2 on?
The platform is Windows, with Rust network protocol 2633 and build 163794 running on #1 YamitoriTown | Moscow | RU | Modded x2. Your game must match the protocol to join, and Steam applies that update.
Is #1 YamitoriTown | Moscow | RU | Modded x2 up, and how steady is its uptime?
Last seen 42 days 7 hours ago, #1 YamitoriTown | Moscow | RU | Modded x2 now reports offline. 0% uptime over the last 7 full days, equal to 0 of 168 hours. 16 September 2026 is when Rust Server Analytics first recorded it.
Lists and tags
How should the tags on #1 YamitoriTown | Moscow | RU | Modded x2 be read?
gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): Player slots: 50; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): To join, your game version must match protocol 2633; cs163794 (Build): Game build: 163794; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^m (Monthly): A monthly cycle, with Facepunch's force wipe as the reset; ^z (Modded): The Modded section, because plugins or settings modify play; ^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. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does #1 YamitoriTown | Moscow | RU | Modded x2 appear across Rust Server Analytics's lists and filters?
The following Rust Server Analytics lists count #1 YamitoriTown | Moscow | RU | Modded x2 among their servers: Rust servers with a 2x gather rate, EU Rust servers: live population data and Modded Rust servers: live data. On the server list, the filters that return it are: 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
What position does #1 YamitoriTown | Moscow | RU | Modded x2 hold in the server rankings?
On player hours over seven days, #1 YamitoriTown | Moscow | RU | Modded x2 ranks #15,514, within the top – of ranked servers.
How many players does #1 YamitoriTown | Moscow | RU | Modded x2 carry?
#1 YamitoriTown | Moscow | RU | Modded x2 is offline at this refresh; the last contact was 42 days 7 hours ago.
Settings
What are the settings on #1 YamitoriTown | Moscow | RU | Modded x2, and its rules?
#1 YamitoriTown | Moscow | RU | Modded x2 names a 2x gather rate. The default group cap of 8 players applies. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. Plugins from Carbon are in use. VAC, Valve's anti-cheat, is 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.
How to join
How can a player join #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 95.73.121.253:28015.