Battlegrounds Testing
Offline 108.74.19.235:28066 checked 19h ago
Server instruments
last reading Wed 00:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 92 · below 20 is lag, below 10 is badEntities
48 h range 66,733–69,234 · memory 2,674 MBUptime
23 h 56 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 33 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:29 UTC FW27d ago | 1 | – | running | 0 |
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 205/500
- 121/100
- 183/225
- 126/700
- 19/200
- 50/1000
Quick answers
from the figures on this pageReset cycle
What happens on Battlegrounds Testing when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 33 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 1 it fell below half when it didn't.
When does Battlegrounds Testing wipe?
Its rhythm cannot be told from the wipes of Battlegrounds Testing on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 27 days ago.
Tag meanings
How should you read the tags on Battlegrounds Testing?
These are the tags Battlegrounds Testing publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the 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 Battlegrounds Testing?
On Rust Metrics, Battlegrounds Testing sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
What position does Battlegrounds Testing hold among Rust servers?
Player hours over seven days put Battlegrounds Testing at #15,373, in the top 69% of all ranked servers.
How full does Battlegrounds Testing get?
Reading for Battlegrounds Testing: offline at this moment; last seen 19 hours ago. A seven-day average of 0 players is the reading.
Server details
What location is Battlegrounds Testing hosted in?
Reading: location. Battlegrounds Testing gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 108.74.19.235:28066.
What Rust version is Battlegrounds Testing on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by Battlegrounds Testing. Matching protocol is required to join. Let Steam update your game.
Is performance on Battlegrounds Testing within range?
Check: fps. Average 111 server fps over the last 48 hours, low of 92. Within range. Check: entities. The peak was 69,234, counting buildings, deployables and the rest of the world. Reading: 2,674 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
How reliable is Battlegrounds Testing, and is it online now?
Check: connection. Battlegrounds Testing is offline at this moment. Last contact was 19 hours ago. By its reported uptime, the last restart was roughly 23 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does Battlegrounds Testing enforce, and what are its settings?
Check: gather rate. The name Battlegrounds Testing does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
Which map is live on Battlegrounds Testing?
Size 3,500 and seed 980990498: the game generates the procedural map on Battlegrounds Testing from them. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.
Connection
What do you do to join Battlegrounds Testing?
To join: start Rust, press F1 and type client.connect 108.74.19.235:28066. Or press Launch Rust here and Steam opens the game and connects you. https://stats.battlegroundsrust.com/ is where its website sits.