LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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 record holds too few of Rust Tournaments | TEST's wipes to reveal its rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 71 days 6 hours have passed since this world was generated.
On Rust Live Stats, Rust Tournaments | TEST is listed under Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
These are the tags Rust Tournaments | TEST makes public: gmrust (Game mode): Survival here follows standard Rust; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2632 (Protocol): The server runs protocol 2632, so match that version to join; cs161125 (Build): Build: 161125; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): No region code is set here; ^z (Modded): Plugins or settings changes put this under Modded; ^y (Carbon): It uses the plugin framework Carbon. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
0 of Rust Tournaments | TEST's 20 slots are filled right now. Across the past week the average was 0 players.
Ranked by seven-day player hours, Rust Tournaments | TEST is #15,349, placing it in the top 69% of ranked servers.
No gather rate appears in the name Rust Tournaments | TEST. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser files it under Modded: plugins or settings alter the game. Plugins run here: Carbon. VAC is enabled: Valve's anti-cheat.
Rust Tournaments | TEST runs a game-generated procedural map: size 3,000, seed 2147483647. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on Rust Tournaments | TEST states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 159.195.206.209:28015.
Server fps averaged 153 over the last 48 hours, with a low of 113. It supported up to 50,378 entities, covering buildings, deployables and all other objects. The highest memory usage was 6,054 MB. Players experience lag when fps is low and the entity count climbs.
Rust Tournaments | TEST operates on Linux with Rust network protocol 2632 and build 161125. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, Rust Tournaments | TEST is live. Based on the uptime it reports, the last restart was about 11 days 9 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. The first sighting by Rust Live Stats was on 13 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 159.195.206.209:28015.