RUST METRICSFlight deck · live data
Data live Servers11,625 Players41,682 Populated3,017 Fresh wipes 3 h86 Scan5 min
‹ All servers197.88.237.5:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server BM

Offline 197.88.237.5:28015 checked 40d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 0 /200

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,383no region published
Last wipe50d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
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

Wipe timing

How often does Test Server BM wipe, and when?

The rhythm of Test Server BM's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 50 days 15 hours ago.

Tag meanings

Which tags does Test Server BM carry, and what do they mean?

Tags published by Test Server BM, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Test Server BM?

Rust Metrics lists featuring Test Server BM: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Where does Test Server BM sit in the rankings?

Player hours over seven days put Test Server BM at #15,383, in the top – of all ranked servers.

What player count does Test Server BM carry?

Test Server BM is not responding; status offline, last seen 40 days 18 hours ago.

Server

Where does Test Server BM sit?

No region tag on Test Server BM. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 197.88.237.5:28015.

What Rust version is Test Server BM on?

Reading: Test Server BM, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is Test Server BM up, and how often does it stay up?

Test Server BM reports offline. The last reading came 40 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Test Server BM enforce, and what are its settings?

No gather rate appears in the name: Test Server BM. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is Test Server BM on?

The game generates a procedural map for Test Server BM.

Connection

What do you do to join Test Server BM?

Press F1 in Rust and enter client.connect 197.88.237.5:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players The server holds 200 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build Game build reading: 164530.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

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.