Rust Data

rustdata.spaceservers108.74.19.235:29059.ipynb

Run all rust-data · live

‹ All servers

Offline 108.74.19.235:29058 checked 12d ago

BattleGrounds Testing 2

Connect

srv = rust.server("108.74.19.235:29059")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,106 # top 70%
last wipe 26d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 16:20 UTC26d ago 0 NaN 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.

display(srv.map, srv.info())

Map

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
108.74.19.235:29058
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 16:20 UTC
hostname
–
first seen
21 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average524/575
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average422/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 290 on average179/250
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average57/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 275 on average249/250
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 236 on average331/350

Quick answers

From the figures on this page.

Population data

What position does BattleGrounds Testing 2 take in the server rankings?

Player hours over seven days put BattleGrounds Testing 2 at #15,106, in the top 70% of the ranked set.

How many players does BattleGrounds Testing 2 hold at once?

Offline now for BattleGrounds Testing 2, with the last sample 12 days 20 hours ago.

About the server

Which Rust version is BattleGrounds Testing 2 on?

The build is Rust network protocol 2634 and build 167398 on Windows, run by BattleGrounds Testing 2. Joining needs the same protocol on your game; Steam handles the update.

How reliable is BattleGrounds Testing 2, and is it online now?

Offline now for BattleGrounds Testing 2, last seen 12 days 20 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 21 September 2026.

In which location is BattleGrounds Testing 2 hosted?

No region is published by BattleGrounds Testing 2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 108.74.19.235:29058.

Map and rules

Which rules apply on BattleGrounds Testing 2, and what settings?

No gather rate appears in the name: BattleGrounds Testing 2. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.

Wipes and dates

On what schedule does BattleGrounds Testing 2 wipe?

Too few wipes are on record for BattleGrounds Testing 2 to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 26 days 22 hours ago, and that is the one in play.

What is wipe day on BattleGrounds Testing 2 like?

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Lists and tags

Which Rust Data filters and lists contain BattleGrounds Testing 2?

These Rust Data lists include BattleGrounds Testing 2: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on BattleGrounds Testing 2 hold?

The game's server browser reads these tags from BattleGrounds Testing 2: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Build number: 167398; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way to join BattleGrounds Testing 2?

In Rust, F1 opens the console: type client.connect 108.74.19.235:29058. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Build number: 167398.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is 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.

Rust Data 83,167 players 11,844 servers online