Rust Data

rustdata.spaceservers79.127.206.186:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 79.127.206.186:28015 checked 42d ago

#1 YamitoriTown | Moscow | RU | Modded x2

2x monthly wipes moddedcarbon

Connect

srv = rust.server("79.127.206.186:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,519 # no region published
last wipe 42d ago # monthly schedule
next wipe 6d 22h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep

Wipe schedule

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. # The force wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
79.127.206.186:28015
region
–
max players
50
group limit
8, the default
wipe schedule
monthly
last wipe
16 Sep 2026, 20:40 UTC
hostname
–
first seen
16 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 819 on average662/750
1Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 611 on average1510/1575
2EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 350 on average785/850
3Vitality - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 295 on average993/1100
4EU Limitless 2x Monthly Main | No BP Wipes | x2EU · groups of 12+ · 2x · monthly · 278 on average299/330
5MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 141 on average82/500

Quick answers

From the figures on this page.

Population data

How does #1 YamitoriTown | Moscow | RU | Modded x2 compare in the rankings?

Rank #15,519 on seven-day player hours for #1 YamitoriTown | Moscow | RU | Modded x2, within the top – of all ranked servers.

What population does #1 YamitoriTown | Moscow | RU | Modded x2 carry?

#1 YamitoriTown | Moscow | RU | Modded x2 returns no live count at this refresh, having last been seen 42 days 22 hours ago.

About the server

What Rust version does #1 YamitoriTown | Moscow | RU | Modded x2 run?

Rust network protocol 2633 and build 163794 on Windows is what #1 YamitoriTown | Moscow | RU | Modded x2 runs. Joining needs the same protocol on your game; Steam handles the update.

Is #1 YamitoriTown | Moscow | RU | Modded x2 up, and what does its uptime show?

#1 YamitoriTown | Moscow | RU | Modded x2 is offline at this refresh; the last response came 42 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 16 September 2026.

Which location does #1 YamitoriTown | Moscow | RU | Modded x2 run from?

No region tag is published by #1 YamitoriTown | Moscow | RU | Modded x2, though its name points to Europe. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 79.127.206.186:28015 is its address.

Map and rules

Which rules apply on #1 YamitoriTown | Moscow | RU | Modded x2, and what settings?

Gather sits at 2x, read from the server's own name: #1 YamitoriTown | Moscow | RU | Modded x2. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.

What is the map on #1 YamitoriTown | Moscow | RU | Modded x2?

#1 YamitoriTown | Moscow | RU | Modded x2 runs a procedural map, which the game generates.

Wipe schedule

When does #1 YamitoriTown | Moscow | RU | Modded x2 wipe, and how often?

Expect an estimate: #1 YamitoriTown | Moscow | RU | Modded x2's next wipe is projected from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 42 days 23 hours ago. Its tags carry a monthly wipe schedule.

Lists and tags

Where does #1 YamitoriTown | Moscow | RU | Modded x2 appear among Rust Data lists and filters?

On Rust Data, #1 YamitoriTown | Moscow | RU | Modded x2 appears in these lists: EU Rust servers, Modded Rust servers and 2x Rust servers. Under these filters on the server list, it is listed: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.

Which meanings do the tags on #1 YamitoriTown | Moscow | RU | Modded x2 hold?

The game's server browser reads these tags from #1 YamitoriTown | Moscow | RU | Modded x2: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Build number: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to #1 YamitoriTown | Moscow | RU | Modded x2?

Enter client.connect 79.127.206.186:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2633,^z,^y,^m,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs163794
Build Build number: 163794.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^y
Carbon The plugin framework in use is Carbon.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 100,368 players 11,855 servers online