Working its way up from the back of the class: #15,405 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 175 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F·WW
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 UTCFW27d 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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Benchmark Dev. Rust Server Score takes the server's word for its location and does not trace the hardware. 199.47.146.194:27016 is the address to use.
How reliable is Benchmark Dev, and is it up?
The server is down: Benchmark Dev is offline now, with the last sighting 8 days 16 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is Benchmark Dev running?
Rust network protocol 2634 and build 166652 on Linux is what Benchmark Dev runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Benchmark Dev reset?
No next wipe can be predicted for Benchmark Dev, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 25 days 13 hours.
What happens on Benchmark Dev when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. The crowd on the latest wipe was largest 2 hours after it began.
Player count
Where does Benchmark Dev place in the wider field of Rust servers?
In the top 69% of all ranked servers, Benchmark Dev sits at #15,405 for player hours over the last seven days.
What does the population on Benchmark Dev look like?
Benchmark Dev is offline at the moment; the last time it was seen was 8 days 16 hours ago.
Lists and filters
What is meant by the tags on Benchmark Dev?
You'll see Benchmark Dev tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server holds 10 slots; ts200 (Group limit): Teams cap out at 200; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Benchmark Dev appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Benchmark Dev among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
Which rules does Benchmark Dev enforce, and what are its settings?
Nothing in the name of Benchmark Dev states a gather rate. A group here can reach 200 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Benchmark Dev uses?
The game generates the procedural map on Benchmark Dev at size 4,500 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Getting in
How should you connect to Benchmark Dev?
To connect, start Rust, press F1, and type client.connect 199.47.146.194:27016. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://cynic-hosting.com.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166652,ts200,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersThe server holds 10 slots.
ts200
Group limitTeams cap out at 200.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).