RUST METRICSFlight deck · live data
Data live Servers11,668 Players44,366 Populated2,905 Fresh wipes 3 h100 Scan5 min
‹ All servers185.66.205.132:28015
Offline Full Queue Fresh wipe Wipe due No query

Broomhill Test

Offline 185.66.205.132:28015 checked 19d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,858top 72%
Last wipe26d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players
No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct6 Oct9 Oct11 Oct14 Oct17 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does Broomhill Test follow?

Its rhythm cannot be told from the wipes of Broomhill Test on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 26 days 11 hours ago.

Tags

How should you read the tags on Broomhill Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Build 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from Broomhill Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Broomhill Test appear in Rust Metrics lists and filters?

On Rust Metrics, Broomhill Test sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does Broomhill Test hold among Rust servers?

Ranking for Broomhill Test: #15,858 on seven-day player hours, top 72% of all ranked servers.

What player count does Broomhill Test carry?

Status for Broomhill Test: offline. Last seen 19 days 4 hours ago.

Server details

Where does Broomhill Test sit?

No region comes from Broomhill Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 185.66.205.132:28015.

What Rust version is Broomhill Test on?

Version check: Rust network protocol 2634 and build 166586 on Linux, run by Broomhill Test. To get in, your game needs the same protocol; Steam applies the update.

Is Broomhill Test up, and how often does it stay up?

Broomhill Test reports offline. The last reading came 19 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 3 October 2026.

Rules and settings

How is Broomhill Test configured, and what rules are in force?

Reading the name gives no gather rate for Broomhill Test. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on Broomhill Test?

Procedural map on Broomhill Test, made by the game's generator.

Join

What do you do to join Broomhill Test?

To join: start Rust, press F1 and type client.connect 185.66.205.132:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players Slots: 500.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Build 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.