Offline 96.39.213.36:28015 checked 22d ago
NO-SHO2
Connect
srv = rust.server("96.39.213.36:28017")
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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 | Tue 6 Oct, 19:21 UTC22d ago | 1 | NaN | running | 1 |
| 1 | Fri 2 Oct, 23:56 UTC26d ago | 1 | NaN | 3.8 days | 1 |
| 2 | Thu 1 Oct, 18:10 UTC FW28d ago | 1 | NaN | 1.2 days | 1 |
| 3 | Fri 18 Sep, 14:56 UTC41d ago | 1 | held half | 13.1 days | 0 |
| 4 | Thu 17 Sep, 19:38 UTC41d ago | 1 | NaN | 0.8 days | 2 |
# 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
- 96.39.213.36:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 19:21 UTC
- hostname
- –
- first seen
- 15 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 · 512 on average | 329/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 435/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 280 on average | 963/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 53/100 |
| 4 | eulongtest (private perf box) | EU · groups of 14+ · monthly · 267 on average | 480/8 |
| 5 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 265 on average | 979/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does NO-SHO2 rank?
Over the last seven days NO-SHO2 sits at #13,779 on player hours, in the top 62% of ranked servers.
How many players does NO-SHO2 hold at once?
The current row shows NO-SHO2 offline; the last response was 22 days 22 hours ago.
Server facts
Which Rust version is NO-SHO2 on?
Rust network protocol 2634 and build 166652 on Windows is what NO-SHO2 runs. Steam updates your game for you, but the protocol must match to join.
How reliable is NO-SHO2, and is it online now?
The latest sample has NO-SHO2 offline, with a last sighting 22 days 22 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 15 September 2026.
Where does NO-SHO2 sit?
For NO-SHO2, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 96.39.213.36:28015.
Rules, settings, map
Which rules apply on NO-SHO2, and what settings?
No gather rate appears in the name: NO-SHO2. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
Which map has NO-SHO2 selected?
NO-SHO2 runs a procedural map, which the game generates.
Wipes and dates
When does NO-SHO2 wipe, and how often?
NO-SHO2 wipes on no fixed rhythm, so there is nothing to predict. 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 22 days 23 hours ago.
On NO-SHO2, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Which Rust Data filters and lists contain NO-SHO2?
These Rust Data lists include NO-SHO2: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on NO-SHO2 hold?
Read by the game's server browser, the tags NO-SHO2 publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into NO-SHO2?
In Rust, F1 opens the console: type client.connect 96.39.213.36:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.