RUST METRICSFlight deck · live data
Data live Servers11,667 Players48,316 Populated3,167 Fresh wipes 3 h118 Scan5 min
‹ All servers106.72.220.164:28015
Offline Full Queue Fresh wipe Wipe due No query

YamagaraServer

Offline 106.72.220.164:28015 checked 10d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

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#13,013top 59%
Last wipe12d agono schedule published
Next wipe–too few wipes seen yet
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 Sep26 Sep2 Oct8 Oct19 Oct25 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

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.

usual gap13 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 17 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 06:04 UTC12d ago 1 – running 0
Sun 4 Oct, 06:09 UTC25d ago 0 – 13 days 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. 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

Reset cycle

What happens on YamagaraServer when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does YamagaraServer follow?

To tell the rhythm of YamagaraServer, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 12 days 3 hours ago the current world was made.

Tag meanings

Which tags does YamagaraServer carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from YamagaraServer. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does YamagaraServer appear in Rust Metrics lists and filters?

These Rust Metrics lists carry YamagaraServer: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does YamagaraServer sit in the rankings?

Ranking for YamagaraServer: #13,013 on seven-day player hours, top 59% of all ranked servers.

What player count does YamagaraServer carry?

Reading for YamagaraServer: offline at this moment; last seen 10 days 18 hours ago.

Server

What location is YamagaraServer hosted in?

No region tag on YamagaraServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 106.72.220.164:28015.

What Rust version is YamagaraServer on?

Rust network protocol 2634 and build 166652 on Windows is the build YamagaraServer runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on YamagaraServer, and is it online?

YamagaraServer reports offline. The last reading came 10 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What rules does YamagaraServer enforce, and what are its settings?

Check: gather rate. The name YamagaraServer does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is YamagaraServer on?

Check: map. Procedural, generated by the game, on YamagaraServer.

Connection

What do you do to join YamagaraServer?

Check: join. Open Rust, press F1, then enter client.connect 106.72.220.164:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.