Offline 36.13.136.190:28115 checked 17h ago
dc-mutsu Rust Staging
Connect
srv = rust.server("36.13.136.190:28117")
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 best
Top 25% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 12:59 UTC12d ago | 1 | NaN | running | 1 |
| 1 | Thu 24 Sep, 20:52 UTC34d ago | 1 | held half | 21.7 days | 0 |
# 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
- 36.13.136.190:28115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 12:59 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 549 on average | 147/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 125/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 14/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 284 on average | 18/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 13/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 249 on average | 38/200 |
Quick answers
From the figures on this page.
Population
How does dc-mutsu Rust Staging compare in the rankings?
Player hours over seven days put dc-mutsu Rust Staging at #5,586, in the top 25% of the ranked set.
How many players does dc-mutsu Rust Staging hold at once?
Offline now for dc-mutsu Rust Staging, with the last sample 17 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 1 players.
About the server
Which Rust version is dc-mutsu Rust Staging on?
The build is Rust network protocol 2635 and build 168255 on Linux, run by dc-mutsu Rust Staging. Joining needs the same protocol on your game; Steam handles the update.
Is dc-mutsu Rust Staging up, and what does its uptime show?
Offline now for dc-mutsu Rust Staging, last seen 17 hours ago. Uptime of 21% across the last 7 full days: 35 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does dc-mutsu Rust Staging run from?
No region is published by dc-mutsu Rust Staging. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 36.13.136.190:28115 is its address.
Rules, settings, map
What rules and settings are recorded for dc-mutsu Rust Staging?
No gather rate appears in the name: dc-mutsu Rust Staging. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
Which map has dc-mutsu Rust Staging selected?
A procedural map runs on dc-mutsu Rust Staging, generated by the game.
Wipe data
When does dc-mutsu Rust Staging wipe, and how often?
Too few wipes are on record for dc-mutsu Rust Staging to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 12 days 15 hours ago.
On dc-mutsu Rust Staging, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags and filters
Where does dc-mutsu Rust Staging appear among Rust Data lists and filters?
These Rust Data lists include dc-mutsu Rust Staging: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on dc-mutsu Rust Staging hold?
Read by the game's server browser, the tags dc-mutsu Rust Staging publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168255 (Build): Build number: 168255; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. 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
How can I connect to dc-mutsu Rust Staging?
In Rust, F1 opens the console: type client.connect 36.13.136.190:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.