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.
Too few wipes are recorded for Halo Test to establish a pattern. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 83 days 17 hours have passed since this world was generated.
The Rust Live Stats lists that include Halo Test are Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more it appears on the server list.
These are the tags Halo Test makes public: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap: 8, which is the game default; v2632 (Protocol): The server runs protocol 2632, so match that version to join; cs160450 (Build): The game build is 160450; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game changes here through plugins or settings, so it is Modded. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Halo Test is carrying 0 players at the moment, with 50 slots in total. Averaged over seven days: 0 players.
Player hours over seven days put Halo Test at #15,344, in the top 69% of all ranked servers.
Nothing in the name of Halo Test states a gather rate. The default applies: 8 players to a group. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.
Halo Test runs a game-generated procedural map: size 3,500, seed 664382915. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on Halo Test states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 205.209.120.235:28080 is its address.
The average server fps was 142 over the last 48 hours; the lowest was 74. Buildings, deployables and everything else in the world added up to a maximum of 65,978 entities. The highest memory usage was 2,646 MB. A climbing entity count and low fps are felt as lag by players.
Halo Test operates on Windows with Rust network protocol 2632 and build 160450. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, Halo Test is live. The uptime it reports puts the last restart at about 2 days 2 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. Rust Live Stats has tracked it since 13 September 2026.
Enter client.connect 205.209.120.235:28080 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.