Online 5.196.124.171:10005 checked 9m ago
BR TEST CLOSED
Connect
srv = rust.server("5.196.124.171:10006")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
Top 66% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 19 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 00:34 UTC27d ago | 1 | 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [LATAM] Vicio Sudamerica Rust | SA · groups of 8+ · biweekly · 2 on average | 3/100 |
| 1 | RustArgentinaSergiopalm PVP/PVE | SA · groups of 8+ · monthly · 1 on average | 1/100 |
| 2 | BRASUKA - VANILLA | MENSAL | SEM LIMITE | SA · groups of 8+ · monthly · 1 on average | 2/200 |
| 3 | Rustoria.co - BR Main | SA · groups of 16+ · weekly · 175 on average | 36/250 |
| 4 | Rustoria.co - BR Long | SA · groups of 12+ · monthly · 65 on average | 40/200 |
| 5 | [BR/LATAM] Rust Na Veia | MAX 4 | | SA · groups of 8+ · weekly · 34 on average | 5/200 |
Quick answers
From the figures on this page.
Population data
What position does BR TEST CLOSED take in the server rankings?
Over the last seven days BR TEST CLOSED sits at #14,645 on player hours, in the top 66% of ranked servers.
How full does BR TEST CLOSED run?
The sample now reads 0 players for BR TEST CLOSED, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
How well does BR TEST CLOSED perform?
Server fps over the last 48 hours averages 100; the floor is 97. Entity numbers reached 75,185, and that includes buildings, deployables and the rest. A high of 4,668 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is BR TEST CLOSED on?
Rust network protocol 2635 and build 168909 on Linux is what BR TEST CLOSED runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is BR TEST CLOSED, and is it online now?
Online is the state at the latest refresh for BR TEST CLOSED. A restart about 15 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
Which location does BR TEST CLOSED run from?
No region tag is published by BR TEST CLOSED, though its name points to South America. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 5.196.124.171:10005.
Settings and map
What rules and settings are recorded for BR TEST CLOSED?
The name BR TEST CLOSED carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has BR TEST CLOSED loaded?
Size 3,600, seed 1337: the procedural map on BR TEST CLOSED, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipe schedule
When does BR TEST CLOSED wipe, and on what schedule?
A rhythm cannot be read from the wipes of BR TEST CLOSED on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 27 days 18 hours ago.
On BR TEST CLOSED, what happens on wipe day?
The average peak over recent wipes is 1 players. 19 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain BR TEST CLOSED?
The Rust Data lists that BR TEST CLOSED fits are: Modded Rust servers. These filters bring it up on the server list: Region: South America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on BR TEST CLOSED hold?
The game's server browser reads these tags from BR TEST CLOSED: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to BR TEST CLOSED?
In Rust, F1 opens the console: type client.connect 5.196.124.171:10005. Launch Rust on this page does the same by opening the game through Steam and connecting. https://brorust.com is the website recorded for it.