Open every day, at every hour Admission free 11,736 servers and 50,841 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

The server's own banner, as it publishes it

Exhibit no. 15,349Acc. 2026.15349

Battlegrounds Testing

Rust server · in the archive since 13 September 2026

Offline 108.74.19.235:28066 checked 23h ago

moddedoxide
To visit
Players now 0/ 10
0% full
7-day average0peak –
Rank#15,349top 69%
Last wipe27d agoThu 1 Oct, 18:29 UTC · no schedule published
Next wipe–too few wipes seen yet

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectedlast seen, 28 Oct 2026, 00:10 UTCAll times UTC.

The record of each wipe

  1. Thu 1 Oct 202618:29 UTC FW27d ago
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Sat 19 Sep 202618:55 UTC39d ago
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    12 days
    Players before
    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.

The rhythm

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.

12 daysusual gapbetween real wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse 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.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
0123401:0006:0010:0015:0019:0000:00

Hourly average and peak, UTC.

Folder 2

Server performance

05010015020001:0006:0010:0015:0019: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.

Folder 3

Rank

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Lists and tags

What do the server tags on Battlegrounds Testing mean?

The game's server browser reads these tags published by Battlegrounds Testing: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): To join, your game has to be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The server has no region code; ^o (Oxide): Oxide, also known as uMod, is the plugin framework in use; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded. Shown at the top of this page are the current players, the queue and the world's age, also taken from the tags.

Which Rust Server History lists and filters include Battlegrounds Testing?

The Rust Server History lists that feature Battlegrounds Testing are: Modded Rust servers: the record. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Server record

Does Battlegrounds Testing run smoothly?

Across the last 48 hours it averaged 113 server fps; the low was 97. As many as 69,147 entities were in the world: buildings, deployables and the rest. Memory use peaked at 2,674 MB. What players feel as lag comes from low fps and a climbing entity count.

Which version of Rust does Battlegrounds Testing run?

Rust network protocol 2635 and build 168909 is the build Battlegrounds Testing runs, on Windows. Joining requires your game to be on the same protocol; Steam keeps it updated for you.

Is Battlegrounds Testing online, and how reliable is it?

Battlegrounds Testing was last seen 23 hours ago and is offline right now. About 23 hours ago is when it last restarted, judged by the uptime it reports. It was up for 144 of 168 hours in the last 7 full days, 86% of the time. First seen by Rust Server History on 13 September 2026.

Where is Battlegrounds Testing located?

You will find no region published by Battlegrounds Testing. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. You can reach it at 108.74.19.235:28066.

Wipe record

What does wipe day look like on Battlegrounds Testing?

At their busiest, its recent wipes drew an average of 1 players. At 33 hours after the latest wipe, the crowd reached its peak. Above half that peak until the next wipe it stayed in 0% of its recent wipes. By day 1 it fell below half in the wipes where it did not hold.

What is the wipe schedule on Battlegrounds Testing?

The record holds too few of Battlegrounds Testing's wipes to tell its rhythm. Next on Thursday 5 November at 19:00 UTC is the monthly force wipe, when every Rust server wipes. 27 days 5 hours ago its current world was made.

Player counts

How does Battlegrounds Testing rank against other Rust servers?

Over seven days of player hours, Battlegrounds Testing ranks #15,349, inside the top 69% of all ranked servers.

How busy is Battlegrounds Testing?

The last sighting of Battlegrounds Testing in the live count was 23 hours ago; it is offline now. Stored history gives a seven-day average of 0 players.

Rules, map

What are the rules and settings on Battlegrounds Testing?

No gather rate is stated in the name of Battlegrounds Testing. The limit of 8 players per group is the game's default. Under game mode, the entry reads survival, gather, build, raid: the standard game. Fighting and raiding between players are permitted. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins are running. VAC from Valve is switched on.

Which map does Battlegrounds Testing run?

A procedural map of size 3,500 with seed 980990498 is what Battlegrounds Testing runs, generated by the game. From this page you can view the map on RustMaps: the same size and seed give the same map. Its map carries the name: Custom Map.

Joining the server

How do I join Battlegrounds Testing?

Entering client.connect 108.74.19.235:28066 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf. You will find its website at https://stats.battlegroundsrust.com/.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit The default cap of 8 per team applies here.
v2635
Protocol To join, your game has to be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide, also known as uMod, is the plugin framework in use.
^z
Modded Plugins or settings alter the game, so it is listed 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.