Rust Data

rustdata.spaceservers95.73.121.253:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 95.73.121.253:28015 checked 42d ago

#1 YamitoriTown | Moscow | RU | Modded x2

2x monthly wipes moddedcarbon

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,514 # no region published
last wipe 42d ago # monthly schedule
next wipe 7d 11h # 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 7d 11h. # 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
95.73.121.253: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 · 810 on average357/400
1Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 601 on average137/150
2EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 350 on average42/150
3Vitality - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 303 on average37/50
4EU Limitless 2x Monthly Main | No BP Wipes | x2EU · groups of 12+ · 2x · monthly · 279 on average78/200
5MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 150 on average52/500

Quick answers

From the figures on this page.

Population data

What position does #1 YamitoriTown | Moscow | RU | Modded x2 take in the server rankings?

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

How full does #1 YamitoriTown | Moscow | RU | Modded x2 run?

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

Server facts

Which Rust version is #1 YamitoriTown | Moscow | RU | Modded x2 on?

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

How reliable is #1 YamitoriTown | Moscow | RU | Modded x2, and is it up?

#1 YamitoriTown | Moscow | RU | Modded x2 is offline at this refresh; the last response came 42 days 8 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 16 September 2026.

Where does #1 YamitoriTown | Moscow | RU | Modded x2 sit?

The name of #1 YamitoriTown | Moscow | RU | Modded x2 points to Europe, even though no region tag is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 95.73.121.253:28015.

Rules, settings, map

Which settings and rules does #1 YamitoriTown | Moscow | RU | Modded x2 run?

The name carries the figure: #1 YamitoriTown | Moscow | RU | Modded x2 runs 2x gather. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

Which map has #1 YamitoriTown | Moscow | RU | Modded x2 loaded?

The game generates its map: procedural, on #1 YamitoriTown | Moscow | RU | Modded x2.

Wipe data

On what schedule does #1 YamitoriTown | Moscow | RU | Modded x2 wipe?

Expect an estimate: #1 YamitoriTown | Moscow | RU | Modded x2's next wipe is projected from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 42 days 10 hours ago. Its tags carry a monthly wipe schedule.

Tags and filters

Which lists on Rust Data hold #1 YamitoriTown | Moscow | RU | Modded x2, and which filters?

The Rust Data lists that #1 YamitoriTown | Moscow | RU | Modded x2 fits are: EU Rust servers, Modded Rust servers and 2x Rust servers. These filters bring it up 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.

How should you read the server tags on #1 YamitoriTown | Moscow | RU | Modded x2?

These tags are published by #1 YamitoriTown | Moscow | RU | Modded x2 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Recorded game build: 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): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join #1 YamitoriTown | Moscow | RU | Modded x2?

The manual route: launch Rust, F1, then client.connect 95.73.121.253:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

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 50 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol The server speaks protocol 2633, so match your game version.
cs163794
Build Recorded game build: 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 Modded listing: the game is changed by plugins or settings.
^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 36,116 players 11,615 servers online