Offline 79.139.208.40:28015 checked 32d ago
TournamentArena LOCAL TEST
Connect
srv = rust.server("79.139.208.40:28017")
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. 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 61% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 13:29 UTC32d ago | 1 | NaN | running | 1 |
| 1 | Thu 24 Sep, 14:10 UTC34d ago | 1 | NaN | 2 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 79.139.208.40:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 13:59 UTC
- hostname
- –
- first seen
- 24 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 159/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 189/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 10/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
Quick answers
From the figures on this page.
Population data
What position does TournamentArena LOCAL TEST take in the server rankings?
Rank #14,305 on seven-day player hours for TournamentArena LOCAL TEST, within the top 61% of all ranked servers.
How many players does TournamentArena LOCAL TEST hold at once?
The current row shows TournamentArena LOCAL TEST offline; the last response was 32 days 19 hours ago.
About the server
What Rust version does TournamentArena LOCAL TEST run?
Rust network protocol 2633 and build 165217 on Windows is what TournamentArena LOCAL TEST runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TournamentArena LOCAL TEST, and is it online now?
TournamentArena LOCAL TEST is offline at this refresh; the last response came 32 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 24 September 2026.
Where does TournamentArena LOCAL TEST sit?
For TournamentArena LOCAL TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 79.139.208.40:28015 is its address.
Settings and map
Which settings and rules does TournamentArena LOCAL TEST run?
No gather rate appears in the name: TournamentArena LOCAL TEST. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe data
On what schedule does TournamentArena LOCAL TEST wipe?
A rhythm cannot be read from the wipes of TournamentArena LOCAL TEST on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 32 days 21 hours ago, and that is the one in play.
On TournamentArena LOCAL TEST, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags, lists
Which Rust Data filters and lists contain TournamentArena LOCAL TEST?
These Rust Data lists include TournamentArena LOCAL TEST: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on TournamentArena LOCAL TEST hold?
Read by the game's server browser, the tags TournamentArena LOCAL TEST publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): The server runs build 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into TournamentArena LOCAL TEST?
In Rust, F1 opens the console: type client.connect 79.139.208.40:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.