Rust Server Analytics 71,901 players11,757 servers
All servers
Drill-through Server detail

Benchmark Dev

Offline 199.47.146.194:27016 checked 8d ago

Drill-through
FilterServeris Benchmark Dev
Attributes
moddedcarbon
Last refreshed
Players now 0/ 10
7-day average 0 peak –
Rank #15,405 top 69%
Last wipe 25d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Sun 4 OctSat 3 OctThu 1 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 02:30 UTC25d ago 2 – running 0
Sat 3 Oct, 02:14 UTC26d ago 2 – 1 days 0
Thu 1 Oct, 19:59 UTC FW28d ago 2 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 149 on average 33 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 127 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 120 on average 65 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average 20 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 93 on average 67 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average 267 / 310

Quick answers

from the figures on this page

Wipe data

The wipe schedule for Benchmark Dev: what is it?

No next wipe can be predicted for Benchmark Dev, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world now in play was created 25 days 20 hours ago.

On Benchmark Dev, what happens on wipe day?

Across recent wipes the busiest point averaged 2 players. The highest player count on the latest wipe arrived 2 hours in.

Server

In which region does Benchmark Dev sit?

A region is not published by Benchmark Dev. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 199.47.146.194:27016 is its address.

What Rust build does Benchmark Dev run?

On Linux, Benchmark Dev runs Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam handles the update.

Is Benchmark Dev up, and how steady is its uptime?

Last seen 8 days 23 hours ago, Benchmark Dev now reports offline. 0% uptime over the last 7 full days, equal to 0 of 168 hours. The first sighting of it by Rust Server Analytics was on 13 September 2026.

Tags

What do Benchmark Dev's tags stand for?

The game's server browser reads the tags Benchmark Dev publishes: gmrust (Game mode): Rust survival, standard ruleset; mp10 (Max players): Capacity of 10 slots; ts200 (Group limit): The cap is 200 players per team; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs166652 (Build): Build number 166652; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^z (Modded): Plugins or settings change the game, so it sits under Modded; ^y (Carbon): It runs Carbon for plugins. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does Benchmark Dev appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count Benchmark Dev among their servers: Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

What position does Benchmark Dev hold in the server rankings?

On player hours over seven days, Benchmark Dev ranks #15,405, within the top 69% of ranked servers.

What is the population of Benchmark Dev?

Benchmark Dev is offline at this refresh; the last contact was 8 days 23 hours ago.

Map and rules

How is Benchmark Dev configured, and what rules apply?

Gather rate is not mentioned in the name of Benchmark Dev. A maximum of 200 players per group applies. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Carbon are in use. Anti-cheat status: VAC on.

What is the map for Benchmark Dev?

A procedural map of size 4,500 with seed 1337, generated by the game, runs on Benchmark Dev. The map is reproducible from its size and seed and can be seen on RustMaps from here. The map is called Custom Map.

How to join

How do you connect to Benchmark Dev?

In the Rust console (F1), enter client.connect 199.47.146.194:27016. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://cynic-hosting.com is its website.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts200,^z,^y

Game

gmrust
Game mode Rust survival, standard ruleset.
mp10
Max players Capacity of 10 slots.
ts200
Group limit The cap is 200 players per team.
v2634
Protocol Protocol 2634 is required: your game must match to connect.
cs166652
Build Build number 166652.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code The region code is blank.

Mods and access

^z
Modded Plugins or settings change the game, so it sits under Modded.
^y
Carbon It runs Carbon for plugins.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.