Rust StatisticsWorking papers on every public Rust server · 32,056 players now

#1 YamitoriTown | Moscow | RU | Modded x2

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 42d ago · 95.73.121.253:28015

Abstract

We describe the public Rust server #1 YamitoriTown | Moscow | RU | Modded x2, reached at 95.73.121.253:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,514 of all servers. It last wiped 42d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywords2x gather monthly wipes modded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,514no region published
Last wipe42d agomonthly schedule
Next wipe37d 13hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 13h. The force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address95.73.121.253:28015
Region–
Max players50
Group limit8, the default
Wipe schedulemonthly
Last wipe16 Sep 2026, 20:40 UTC
Hostname–
First seen16 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust servers in europe [2], 2x rust servers list [3], modded Rust population table [4] and upcoming Rust wipes [5].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 807 on average273/300
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 600 on average103/125
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 350 on average45/150
Vitality - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 302 on average33/50
EU Limitless 2x Monthly Main | No BP Wipes | x2EU · groups of 12+ · 2x · monthly · 278 on average61/200
MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 150 on average28/500

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does #1 YamitoriTown | Moscow | RU | Modded x2 have?

No region tag is published by #1 YamitoriTown | Moscow | RU | Modded x2, but its name points to Europe. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 95.73.121.253:28015 is its address.

A.2How reliable is #1 YamitoriTown | Moscow | RU | Modded x2, and is it currently online?

#1 YamitoriTown | Moscow | RU | Modded x2 is currently offline, with the last sighting 42 days 7 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. It was first observed on 16 September 2026 by Rust Statistics.

A.3What version of Rust is run on #1 YamitoriTown | Moscow | RU | Modded x2?

#1 YamitoriTown | Moscow | RU | Modded x2 is running Rust network protocol 2633 and build 163794 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4What schedule does #1 YamitoriTown | Moscow | RU | Modded x2 follow for wipes?

An estimate derived from the force wipe gives the next wipe for #1 YamitoriTown | Moscow | RU | Modded x2. On Thursday 5 November at 19:00 UTC the force wipe occurs, and that is when every Rust server, including this one, next wipes. The world currently in use was created 42 days 8 hours ago. The tags show that the server wipes monthly.

Player count

A.5What is the rank of #1 YamitoriTown | Moscow | RU | Modded x2 among Rust servers?

Ranked by player hours across seven days, #1 YamitoriTown | Moscow | RU | Modded x2 holds #15,514, in the top – of all ranked servers.

A.6At what level does #1 YamitoriTown | Moscow | RU | Modded x2 operate in terms of players?

#1 YamitoriTown | Moscow | RU | Modded x2 is not online now; 42 days 7 hours have passed since it was last seen.

Tags, lists

A.7What do the tags associated with #1 YamitoriTown | Moscow | RU | Modded x2 signify?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs163794 (Build): Build 163794 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^m (Monthly): The cycle is monthly: Facepunch's force wipe is when it wipes; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): The plugin framework is Carbon, which #1 YamitoriTown | Moscow | RU | Modded x2 publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.8Where can #1 YamitoriTown | Moscow | RU | Modded x2 be found among the Rust Statistics lists and filters?

These Rust Statistics lists include #1 YamitoriTown | Moscow | RU | Modded x2: Rust servers with a 2x gather rate, European Rust servers and Modded Rust servers. You will find it on the server list filtered by: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.

Settings and map

A.9Which settings and rules are in force on #1 YamitoriTown | Moscow | RU | Modded x2?

The rate for gathering on #1 YamitoriTown | Moscow | RU | Modded x2 is 2x, according to its name. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

A.10On which map does #1 YamitoriTown | Moscow | RU | Modded x2 take place?

A procedural map, generated by the game, is what #1 YamitoriTown | Moscow | RU | Modded x2 runs.

How to join

A.11What is the process for joining #1 YamitoriTown | Moscow | RU | Modded x2?

Press F1 inside Rust to open the console and enter client.connect 95.73.121.253:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2633,^z,^y,^m,gmrust,cs163794,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp50Max players. 50 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs163794Build. Build 163794 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.
Wipe schedule
^mMonthly. The cycle is monthly: Facepunch's force wipe is when it wipes.
Mods and access
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
^yCarbon. The plugin framework 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Rust servers in europe. ruststatistics.org/top-eu-rust-servers.
  3. [3]Rust Statistics. 2x rust servers list. ruststatistics.org/top-2x-rust-servers.
  4. [4]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  5. [5]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.