Halo Test
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 10m ago · 205.209.120.235:28080
Abstract
We describe the public Rust server Halo Test, reached at 205.209.120.235:28080. At the last check it held 0 of 50 places, against a seven-day mean of 01. It ranks #15,327 of all servers, the top 69%. It last wiped 83d ago.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 205.209.120.235:28080 |
|---|---|
| Region | – |
| Max players | 50 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 6 Aug 2026, 22:01 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | 3500 |
| Seed | 664382915 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and servers wiping soon [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 151 on average | 153/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average | 126/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average | 194/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average | 97/700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 88 on average | 221/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average | 348/350 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1How well does Halo Test run?
The server fps averaged 140 over the last 48 hours, never dropping below 74. The highest number of entities it carried was 65,978, comprising buildings, deployables and all other objects. The peak memory usage was 2,646 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.
A.2What location does Halo Test have?
No region is published by Halo Test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 205.209.120.235:28080 is its address.
A.3What is the online status and reliability of Halo Test?
Halo Test is online at this time. It last restarted around 2 days 5 hours ago, according to its reported uptime. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.
A.4What version of Rust is run on Halo Test?
Rust network protocol 2632 and build 160450 is the version that Halo Test runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.5On what cycle does Halo Test wipe?
The record of Halo Test's wipes is not yet sufficient to establish its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 83 days 19 hours have passed since the current world was generated.
Population
A.6What position does Halo Test occupy in the ranking of Rust servers?
Ranked by player hours across seven days, Halo Test holds #15,327, in the top 69% of all ranked servers.
A.7What is the population level of Halo Test?
On Halo Test, 0 of the 50 slots are occupied at present. Averaged across the last seven days, the population is 0 players.
Tags and filters
A.8What do the tags associated with Halo Test signify?
Tags from Halo Test, read by the game's server browser, are gmrust (Game mode): Rust survival, in its standard form; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2632 (Protocol): The game protocol is 2632; your client must match it to join; cs160450 (Build): The game build is 160450; 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 game is altered by plugins or settings, so it is listed as Modded. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.9Where can Halo Test be found among the Rust Statistics lists and filters?
These Rust Statistics lists include Halo Test: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Settings and map
A.10Under what rules and settings does Halo Test operate?
Its name carries no gather rate for Halo Test. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.
A.11What is the map for Halo Test?
Size 3,500 and seed 664382915 define the procedural, game-generated map on Halo Test. Equal size and seed yield an identical map, which this page offers to view on RustMaps.
Connection
A.12How do you connect to Halo Test?
Press F1 inside Rust to open the console and enter client.connect 205.209.120.235:28080. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp50,ptrak,$r?,v2632,gmrust,cs160450,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Rust survival, in its standard form. |
mp50 | Max players. 50 slots are available. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2632 | Protocol. The game protocol is 2632; your client must match it to join. |
cs160450 | Build. The game build is 160450. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. No region code is set. |
| Mods and access | |
^o | Oxide. The plugin framework in use is Oxide (uMod). |
^z | Modded. The game is altered by plugins or settings, so it is listed as Modded. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.