RUST METRICSFlight deck · live data
Data live Servers11,709 Players54,841 Populated3,244 Fresh wipes 3 h155 Scan5 min
‹ All servers95.73.121.253:28015
Offline Full Queue Fresh wipe Wipe due No query

#1 YamitoriTown | Moscow | RU | Modded x2

Offline 95.73.121.253:28015 checked 42d ago

2x monthly wipes moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,514no region published
Last wipe42d agomonthly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

How often does #1 YamitoriTown | Moscow | RU | Modded x2 wipe, and when?

The estimate for #1 YamitoriTown | Moscow | RU | Modded x2's next wipe comes from the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 42 days 13 hours ago the current world was made. A monthly wipe schedule is published in its tags.

Lists and filters

Which tags does #1 YamitoriTown | Moscow | RU | Modded x2 carry, and what do they mean?

These are the tags #1 YamitoriTown | Moscow | RU | Modded x2 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

These Rust Metrics lists carry #1 YamitoriTown | Moscow | RU | Modded x2: 2x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.

Occupancy

What position does #1 YamitoriTown | Moscow | RU | Modded x2 hold among Rust servers?

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

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

Status for #1 YamitoriTown | Moscow | RU | Modded x2: offline. Last seen 42 days 12 hours ago.

Operator and location

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

Check: location. No region tag comes from #1 YamitoriTown | Moscow | RU | Modded x2, but the name points to Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 95.73.121.253:28015.

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

Reading: #1 YamitoriTown | Moscow | RU | Modded x2, Rust network protocol 2633 and build 163794, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

#1 YamitoriTown | Moscow | RU | Modded x2 reports offline. The last reading came 42 days 12 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 16 September 2026.

Settings and map

What settings and rules apply on #1 YamitoriTown | Moscow | RU | Modded x2?

The name carries the rate: 2x gather on #1 YamitoriTown | Moscow | RU | Modded x2. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

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

The game generates a procedural map for #1 YamitoriTown | Moscow | RU | Modded x2.

Connection

What do you do to join #1 YamitoriTown | Moscow | RU | Modded x2?

Press F1 in Rust and enter client.connect 95.73.121.253:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: 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.