RUST METRICSFlight deck · live data
Data live Servers11,766 Players66,169 Populated3,487 Fresh wipes 3 h192 Scan5 min
‹ All servers185.229.191.71:28015
Offline Full Queue Fresh wipe Wipe due No query

FERRUM TEST

Offline 185.229.191.71:28015 checked 23d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,971top 71%
Last wipe24d 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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

Top 71% 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

How often does FERRUM TEST wipe, and when?

Its rhythm cannot be told from the wipes of FERRUM 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 it runs now was made 24 days 15 hours ago.

Tag meanings

How should you read the tags on FERRUM TEST?

These are the tags FERRUM TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does FERRUM TEST appear in Rust Metrics lists and filters?

These Rust Metrics lists carry FERRUM TEST: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does FERRUM TEST sit in the rankings?

Player hours over seven days put FERRUM TEST at #15,971, in the top 71% of all ranked servers.

What player count does FERRUM TEST carry?

Reading for FERRUM TEST: offline at this moment; last seen 23 days 20 hours ago.

Operator and location

What location is FERRUM TEST hosted in?

Reading: location. FERRUM TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 185.229.191.71:28015.

What Rust version is FERRUM TEST on?

Version check: Rust network protocol 2634 and build 166652 on Linux, run by FERRUM TEST. Check: protocol. To join, your game must match; Steam handles the update.

Is FERRUM TEST up, and how often does it stay up?

FERRUM TEST reports offline. The last reading came 23 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 5 October 2026.

Rules and settings

What rules does FERRUM TEST enforce, and what are its settings?

Check: gather rate. The name FERRUM TEST does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

What map is FERRUM TEST on?

Check: map. Procedural, generated by the game, on FERRUM TEST.

Join

What do you do to join FERRUM TEST?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

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.