Station XX-15519 · no signal
#1 YamitoriTown | Moscow | RU | Modded x2
Offline 79.127.206.186: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,519
- no region published
- Last wipe
- 42d ago
- monthly schedule
- Next wipe
- 7d 11h
- 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 11h. 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?
The map on #1 YamitoriTown | Moscow | RU | Modded x2 is procedural, produced by the game.
Which settings and rules apply on #1 YamitoriTown | Moscow | RU | Modded x2?
Its name points to a gather rate of 2x on #1 YamitoriTown | Moscow | RU | Modded x2. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on #1 YamitoriTown | Moscow | RU | Modded x2?
A reading taken now finds #1 YamitoriTown | Moscow | RU | Modded x2 offline; the most recent activity was 42 days 9 hours ago.
How does #1 YamitoriTown | Moscow | RU | Modded x2 rank against other Rust servers?
The last seven days of player hours place #1 YamitoriTown | Moscow | RU | Modded x2 at #15,519, in the top – of all ranked servers.
Server details
How reliably does #1 YamitoriTown | Moscow | RU | Modded x2 stay online?
#1 YamitoriTown | Moscow | RU | Modded x2 is down at the moment; the last recorded contact was 42 days 9 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 16 September 2026 is when Rust Server Trends first recorded it.
Which region does #1 YamitoriTown | Moscow | RU | Modded x2 run from?
Its name points to Europe, but #1 YamitoriTown | Moscow | RU | Modded x2 publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 79.127.206.186:28015.
Which Rust version is #1 YamitoriTown | Moscow | RU | Modded x2 running?
On Windows, #1 YamitoriTown | Moscow | RU | Modded x2 runs Rust network protocol 2633 and build 163794. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
On what timetable does #1 YamitoriTown | Moscow | RU | Modded x2 run its wipes?
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. 42 days 10 hours is how long the current world has been running. The tags it publishes carry a monthly wipe schedule.
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): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163794 (Build): It runs game build 163794; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs 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?
These Rust Server Trends lists include #1 YamitoriTown | Moscow | RU | Modded x2: 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.
Join the server
What steps get you onto #1 YamitoriTown | Moscow | RU | Modded x2?
Enter client.connect 79.127.206.186:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.