Offline 106.72.220.164:28015 checked 10d ago
YamagaraServer
Connect
srv = rust.server("106.72.220.164:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 06:04 UTC12d ago | 1 | NaN | running | 0 |
| 1 | Sun 4 Oct, 06:09 UTC25d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 106.72.220.164:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 06:04 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 54/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 72/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 22/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Population
How does YamagaraServer compare in the rankings?
Player hours over seven days put YamagaraServer at #13,013, in the top 59% of the ranked set.
How full does YamagaraServer run?
The current row shows YamagaraServer offline; the last response was 10 days 15 hours ago.
Server data
What is the Rust version on YamagaraServer?
Version Rust network protocol 2634 and build 166652 on Windows is reported by YamagaraServer. Joining needs the same protocol on your game; Steam handles the update.
Is YamagaraServer up, and what does its uptime show?
YamagaraServer is offline at this refresh; the last response came 10 days 15 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is YamagaraServer hosted?
For YamagaraServer, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 106.72.220.164:28015.
Rules, settings, map
Which rules apply on YamagaraServer, and what settings?
No gather rate appears in the name: YamagaraServer. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on YamagaraServer?
YamagaraServer runs a procedural map, which the game generates.
Wipe schedule
On what schedule does YamagaraServer wipe?
A rhythm cannot be read from the wipes of YamagaraServer on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 12 days ago.
On YamagaraServer, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain YamagaraServer?
On Rust Data, YamagaraServer appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on YamagaraServer?
These tags are published by YamagaraServer and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): 500 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join YamagaraServer?
Enter client.connect 106.72.220.164:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.