Station XX-13013 · no signal
YamagaraServer
Offline 106.72.220.164:28015 checked 10d ago
- Players now
- 1/ 500
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,013
- top 59%
- Last wipe
- 11d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 500 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 13 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 17 Oct, 06:04 UTC11d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 4 Oct, 06:09 UTC24d ago | M0.0▼falling | 0 | – | – | 13 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on YamagaraServer?
The map on YamagaraServer is procedural, produced by the game.
Which settings and rules apply on YamagaraServer?
No gather rate appears in the name of YamagaraServer. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
How many players are recorded on YamagaraServer right now?
No players are recorded on YamagaraServer at this moment; it is offline, and the last sighting was 10 days 11 hours ago.
How does YamagaraServer rank against other Rust servers?
The last seven days of player hours place YamagaraServer at #13,013, in the top 59% of all ranked servers.
Server details
How reliably does YamagaraServer stay online?
YamagaraServer is down at the moment; the last recorded contact was 10 days 11 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does YamagaraServer run from?
Nothing about a region comes from YamagaraServer. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 106.72.220.164:28015 is the address it uses.
What build of Rust does YamagaraServer use?
YamagaraServer is running Rust network protocol 2634 and build 166652 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on YamagaraServer?
0 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
How often does YamagaraServer wipe, and on which days?
The rhythm of YamagaraServer cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 11 days 20 hours.
Tags
What do the server tags on YamagaraServer mean?
The game's server browser reads the tags YamagaraServer publishes: gmrust (Game mode): You'll find standard Rust survival here; mp500 (Max players): The server has 500 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does YamagaraServer appear?
The Rust Server Trends lists that take in YamagaraServer are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
How do you connect to YamagaraServer?
To join, enter client.connect 106.72.220.164:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.