Rust Data

rustdata.spaceservers108.74.19.235:28067.ipynb

Run all rust-data · live

‹ All servers

Offline 108.74.19.235:28066 checked 1d ago

Battlegrounds Testing

moddedoxide

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123402:0006:0011:0015:0020:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020002:0006:0011:0015:0020:0000:00

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, measured since 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 69% 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.

usual gap12 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 1 OctSat 19 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:29 UTC FW27d ago 1 NaN running 0
1 Sat 19 Sep, 18:55 UTC39d ago 1 halved by day 1 12 days 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

3500 · seed 980990498
Map of Battlegrounds Testing
map
Custom Map
size
3500
seed
980990498

Server

srv.info()
address
108.74.19.235:28066
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 18:29 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average35/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average40/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average31/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average6/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average4/1000

Quick answers

From the figures on this page.

Population

What position does Battlegrounds Testing take in the server rankings?

Player hours over seven days put Battlegrounds Testing at #15,349, in the top 69% of the ranked set.

How full does Battlegrounds Testing run?

Battlegrounds Testing returns no live count at this refresh, having last been seen 25 hours ago. Over the last seven days it averaged 0 players.

Server facts

What does performance look like on Battlegrounds Testing?

Server fps over the last 48 hours averages 112; the floor is 97. The entity count peaked at 69,147, covering buildings, deployables and the rest of the world. Memory peaked at 2,674 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is Battlegrounds Testing on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Battlegrounds Testing. Steam updates your game for you, but the protocol must match to join.

How reliable is Battlegrounds Testing, and is it online now?

Battlegrounds Testing is offline at this refresh; the last response came 25 hours ago. The uptime it reports puts the last restart about 23 hours ago. Uptime of 86% across the last 7 full days: 145 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Battlegrounds Testing sit?

No region is published by Battlegrounds Testing. Rust Data does not look up where the machine stands; it shows where a server says it is. 108.74.19.235:28066 is its address.

Map and rules

Which rules apply on Battlegrounds Testing, and what settings?

You will not find a gather rate in the string Battlegrounds Testing. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has Battlegrounds Testing loaded?

Battlegrounds Testing runs a procedural map of size 3,500 with seed 980990498, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.

Wipes and dates

On what schedule does Battlegrounds Testing wipe?

A rhythm cannot be read from the wipes of Battlegrounds Testing on record, which are too few. 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 27 days 6 hours ago, and that is the one in play.

On Battlegrounds Testing, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 33 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Lists and tags

Which Rust Data filters and lists contain Battlegrounds Testing?

These Rust Data lists include Battlegrounds Testing: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Battlegrounds Testing?

These tags are published by Battlegrounds Testing and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into Battlegrounds Testing?

In Rust, F1 opens the console: type client.connect 108.74.19.235:28066. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://stats.battlegroundsrust.com/.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 44,070 players 11,698 servers online