Offline 199.47.146.194:27016 checked 8d ago
Benchmark Dev
Connect
srv = rust.server("199.47.146.194:27018")
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, measured since 17 Sep. 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 69% 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 2, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 02:30 UTC25d ago | 2 | NaN | running | 0 |
| 1 | Sat 3 Oct, 02:14 UTC26d ago | 2 | NaN | 1 days | 0 |
| 2 | Thu 1 Oct, 19:59 UTC FW27d ago | 2 | NaN | 1.3 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
4500 · seed 1337
- map
- Custom Map
- size
- 4500
- seed
- 1337
Server
srv.info()- address
- 199.47.146.194:27016
- region
- –
- max players
- 10
- group limit
- 200 max
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 02:30 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 | 113/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 196/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 73/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 211/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
What position does Benchmark Dev take in the server rankings?
Player hours over seven days put Benchmark Dev at #15,405, in the top 69% of the ranked set.
How many players does Benchmark Dev hold at once?
The current row shows Benchmark Dev offline; the last response was 8 days 19 hours ago.
Server data
Which Rust version is Benchmark Dev on?
The build is Rust network protocol 2634 and build 166652 on Linux, run by Benchmark Dev. Steam updates your game for you, but the protocol must match to join.
How reliable is Benchmark Dev, and is it up?
The latest sample has Benchmark Dev offline, with a last sighting 8 days 19 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is Benchmark Dev hosted?
There is no region published for Benchmark Dev. Rust Data does not look up where the machine stands; it shows where a server says it is. 199.47.146.194:27016 is its address.
Map and rules
Which settings and rules does Benchmark Dev run?
No gather rate appears in the name: Benchmark Dev. 200 players is the maximum per group. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Benchmark Dev selected?
Size 4,500, seed 1337: the procedural map on Benchmark Dev, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.
Wipe data
When does Benchmark Dev wipe, and on what schedule?
Benchmark Dev 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. A new world was started 25 days 16 hours ago, and that is the one in play.
On Benchmark Dev, what happens on wipe day?
The average peak over recent wipes is 2 players. Peak population on the latest wipe came 2 hours in.
Tags, lists
Which Rust Data filters and lists contain Benchmark Dev?
The Rust Data lists that Benchmark Dev 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.
How should you read the server tags on Benchmark Dev?
The game's server browser reads these tags from Benchmark Dev: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts200 (Group limit): No team may exceed 200; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join Benchmark Dev?
Enter client.connect 199.47.146.194:27016 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://cynic-hosting.com.