Rust StatisticsWorking papers on every public Rust server · 36,584 players now

YamagaraServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 10d ago · 106.72.220.164:28015

Abstract

We describe the public Rust server YamagaraServer, reached at 106.72.220.164:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,013 of all servers, the top 59%. It last wiped 12d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/5000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,013top 59%
Last wipe12d agono schedule published
Next wipe3–too few wipes seen yet

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

The server stands in the top 59% of all ranked servers. 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 Sep26 Sep2 Oct8 Oct19 Oct25 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap13 daysbetween real wipes
Wipe-day peak0players, last three wipes
Sat 17 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sat 17 Oct, 06:0412d ago 1 – running 0
Sun 4 Oct, 06:0925d ago 0 – 13 d 1

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 5: The map: Procedural Map.
Table 4: The server's published settings.
Address106.72.220.164:28015
Region–
Max players500
Group limit8, the default
Wipe schedule–
Last wipe17 Oct 2026, 06:04 UTC
Hostname–
First seen13 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 modded Rust servers listed live [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 150 on average70/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average97/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average32/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average5/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average7/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is YamagaraServer based?

A region is not published by YamagaraServer. Rust Statistics does not look up the machine's location; it shows where the server says it is. 106.72.220.164:28015 is its address.

A.2What is the online status and reliability of YamagaraServer?

Right now, YamagaraServer is offline, and the last time it was seen was 10 days 16 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.

A.3What is the Rust version for YamagaraServer?

Rust network protocol 2634 and build 166652 is the version that YamagaraServer runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does YamagaraServer follow for wipes?

Too few wipes by YamagaraServer have been recorded to determine the pattern. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 12 days 1 hours have passed since the current world was generated.

A.5What characterises wipe day on YamagaraServer?

The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6What position does YamagaraServer occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts YamagaraServer at #13,013, within the top 59% of ranked servers.

A.7How would you characterise the player activity on YamagaraServer?

The last recorded sighting of YamagaraServer was 10 days 16 hours ago; it is offline now.

Tags and filters

A.8What is the meaning of the tags on YamagaraServer?

gmrust (Game mode): Survival on standard Rust rules; mp500 (Max players): 500 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166652 (Build): Build 166652 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags YamagaraServer publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can YamagaraServer be found among the Rust Statistics lists and filters?

These Rust Statistics lists include YamagaraServer: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules, settings, map

A.10Which settings and rules are in force on YamagaraServer?

Its name carries no gather rate for YamagaraServer. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.

A.11On which map does YamagaraServer take place?

The game generates the map on YamagaraServer; that format is procedural.

How to join

A.12What steps are required to join YamagaraServer?

Enter client.connect 106.72.220.164:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp500,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp500Max players. 500 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Your game must run protocol 2634 to connect.
cs166652Build. Build 166652 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.