RUST METRICSFlight deck · live data
Data live Servers11,676 Players50,302 Populated3,170 Fresh wipes 3 h121 Scan5 min
‹ All servers108.74.19.235:29058
Offline Full Queue Fresh wipe Wipe due No query

BattleGrounds Testing 2

Offline 108.74.19.235:29058 checked 12d ago

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,106top 70%
Last wipe26d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k21 Sep27 Sep4 Oct10 Oct17 Oct23 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 16:20 UTC26d ago 0 – running 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.

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

What should you expect from wipe day on BattleGrounds Testing 2?

At their busiest, its recent wipes drew 0 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does BattleGrounds Testing 2 wipe, and when?

To tell the rhythm of BattleGrounds Testing 2, too few of its wipes 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 in play was created 26 days 17 hours ago.

Tags

How should you read the tags on BattleGrounds Testing 2?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Game build reading: 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from BattleGrounds Testing 2. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does BattleGrounds Testing 2 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry BattleGrounds Testing 2: 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

Where does BattleGrounds Testing 2 sit in the rankings?

Ranking for BattleGrounds Testing 2: #15,106 on seven-day player hours, top 70% of all ranked servers.

What is the population on BattleGrounds Testing 2?

Reading for BattleGrounds Testing 2: offline at this moment; last seen 12 days 15 hours ago.

Server details

What location is BattleGrounds Testing 2 hosted in?

Reading: location. BattleGrounds Testing 2 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 108.74.19.235:29058.

What Rust version is BattleGrounds Testing 2 on?

Rust network protocol 2634 and build 167398 on Windows is the build BattleGrounds Testing 2 runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on BattleGrounds Testing 2, and is it online?

BattleGrounds Testing 2 reports offline. The last reading came 12 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 21 September 2026.

Settings and map

What rules does BattleGrounds Testing 2 enforce, and what are its settings?

No gather rate appears in the name: BattleGrounds Testing 2. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Connection

How do you connect to BattleGrounds Testing 2?

Check: join. Open Rust, press F1, then enter client.connect 108.74.19.235:29058. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Game build reading: 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.