Live coverage · Rust server
Offline YamagaraServer is not on the server list right now. The figures below are from when it was last seen, 10d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · 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.
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The current map
Saturday 17 October 2026, 06:04 UTC
Wipe
Sunday 4 October 2026, 06:09 UTC
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.
Recent wipes on this server averaged a peak of 0 players at their busiest. Peak population on the latest wipe came 0 hours after it.
YamagaraServer's wipe history is too thin on record to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world dates from 11 days 20 hours.
The Rust Live Stats lists that include YamagaraServer are Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks it appears on the server list.
gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): You need protocol 2634 on your game to get in; cs166652 (Build): The game build is 166652; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded: that is the tag list YamagaraServer publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
YamagaraServer reads offline at the moment; the last sighting was 10 days 12 hours ago.
Ranked by seven-day player hours, YamagaraServer is #13,013, placing it in the top 59% of ranked servers.
No gather rate appears in the name YamagaraServer. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. Plugins or settings change the game, and the browser lists it as Modded. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.
The map on YamagaraServer is procedural, made by the game itself.
Nothing on YamagaraServer states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 106.72.220.164:28015.
YamagaraServer operates on Windows with Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam takes care of updating it.
As of now, YamagaraServer is offline; the last sighting was 10 days 12 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. The first sighting by Rust Live Stats was on 13 September 2026.
Enter client.connect 106.72.220.164:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.