Station XX-15514 · no signal
#1 YamitoriTown | Moscow | RU | Modded x2
Offline 95.73.121.253:28015 checked 42d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,514
- no region published
- Last wipe
- 42d ago
- monthly schedule
- Next wipe
- 7d 19h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
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 bestWipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on #1 YamitoriTown | Moscow | RU | Modded x2?
#1 YamitoriTown | Moscow | RU | Modded x2 uses a procedural map, which the game generates.
Which settings and rules apply on #1 YamitoriTown | Moscow | RU | Modded x2?
Going by its name, #1 YamitoriTown | Moscow | RU | Modded x2 runs 2x gather. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Carbon. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on #1 YamitoriTown | Moscow | RU | Modded x2 right now?
#1 YamitoriTown | Moscow | RU | Modded x2 is not responding at this moment and is offline, last seen 42 days 1 hours ago.
How does #1 YamitoriTown | Moscow | RU | Modded x2 rank against other Rust servers?
On player hours for the past week, #1 YamitoriTown | Moscow | RU | Modded x2 sits at #15,514, which puts it inside the top – of every ranked server.
Server facts
How reliably does #1 YamitoriTown | Moscow | RU | Modded x2 stay online?
No contact with #1 YamitoriTown | Moscow | RU | Modded x2 right now, and the last recorded contact was 42 days 1 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 16 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does #1 YamitoriTown | Moscow | RU | Modded x2 run from?
The name of #1 YamitoriTown | Moscow | RU | Modded x2 points to Europe, even though it publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 95.73.121.253:28015 is the address it uses.
What build of Rust does #1 YamitoriTown | Moscow | RU | Modded x2 use?
Rust network protocol 2633 and build 163794 on Windows is what #1 YamitoriTown | Moscow | RU | Modded x2 runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does #1 YamitoriTown | Moscow | RU | Modded x2 wipe, and on which days?
From the force wipe the next wipe of #1 YamitoriTown | Moscow | RU | Modded x2 is estimated. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 42 days 3 hours. A monthly wipe schedule is published in its tags.
Tags
What do the server tags on #1 YamitoriTown | Moscow | RU | Modded x2 mean?
These are the tags #1 YamitoriTown | Moscow | RU | Modded x2 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs163794 (Build): It runs game build 163794; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does #1 YamitoriTown | Moscow | RU | Modded x2 appear?
The Rust Server Trends lists that take in #1 YamitoriTown | Moscow | RU | Modded x2 are: 2x Rust servers, listed live, EU Rust servers and Modded Rust servers, tracked live. You will find it under these filters on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Connecting
How do you connect to #1 YamitoriTown | Moscow | RU | Modded x2?
To join, enter client.connect 95.73.121.253:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.