Offline 185.16.39.85:28015 checked 39d ago
ClanNode Rust test
Connect
srv = rust.server("185.16.39.85: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 70% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 20 Sep, 17:03 UTC39d ago | 0 | NaN | running | 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
- 185.16.39.85:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Sep 2026, 17:03 UTC
- hostname
- –
- first seen
- 20 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 | 20/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 · 122 on average | 38/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 7/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 22/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 107/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does ClanNode Rust test rank?
Player hours over seven days put ClanNode Rust test at #15,490, in the top 70% of the ranked set.
How many players does ClanNode Rust test hold at once?
Offline now for ClanNode Rust test, with the last sample 39 days 10 hours ago.
Server data
Which Rust version is ClanNode Rust test on?
The build is Rust network protocol 2633 and build 164530 on Linux, run by ClanNode Rust test. The protocol has to match before you can join, and Steam does the updating.
How reliable is ClanNode Rust test, and is it online now?
Offline now for ClanNode Rust test, last seen 39 days 10 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 20 September 2026.
Where does ClanNode Rust test sit?
There is no region published for ClanNode Rust test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.16.39.85:28015.
Rules, settings, map
Which settings and rules does ClanNode Rust test run?
The name ClanNode Rust test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has ClanNode Rust test selected?
ClanNode Rust test runs a procedural map, which the game generates.
Wipe schedule
When does ClanNode Rust test wipe, and how often?
Too few wipes are on record for ClanNode Rust test to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 39 days 10 hours ago, and that is the one in play.
On ClanNode Rust test, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold ClanNode Rust test, and which filters?
The Rust Data lists that ClanNode Rust test fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on ClanNode Rust test hold?
Read by the game's server browser, the tags ClanNode Rust test publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): Build number: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to ClanNode Rust test?
In Rust, F1 opens the console: type client.connect 185.16.39.85:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.