Online 205.209.120.235:28080 checked 8m ago
Halo Test
Connect
srv = rust.server("205.209.120.235:28015")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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. 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
3500 · seed 664382915
- map
- Procedural Map
- size
- 3500
- seed
- 664382915
Server
srv.info()- 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
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 · 151 on average | 87/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 148/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 60/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 170/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Halo Test rank?
Player hours over seven days put Halo Test at #15,289, in the top 69% of the ranked set.
What population does Halo Test carry?
Current row: 0 players on Halo Test, against 50 slots. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on Halo Test?
Server fps over the last 48 hours averages 139; the floor is 74. The entity count peaked at 65,978, covering buildings, deployables and the rest of the world. A high of 2,828 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on Halo Test?
Version Rust network protocol 2632 and build 160450 on Windows is reported by Halo Test. The protocol has to match before you can join, and Steam does the updating.
Is Halo Test up, and what does its uptime show?
Online is the state at the latest refresh for Halo Test. A restart about 2 days 7 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.
Where does Halo Test sit?
There is no region published for Halo Test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 205.209.120.235:28080.
Map and rules
Which settings and rules does Halo Test run?
You will not find a gather rate in the string Halo Test. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on Halo Test?
The game generates the map on Halo Test: procedural, size 3,500, seed 664382915. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
On what schedule does Halo Test wipe?
A rhythm cannot be read from the wipes of Halo 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 83 days 21 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain Halo Test?
These Rust Data lists include Halo 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.
How should you read the server tags on Halo Test?
Read by the game's server browser, the tags Halo Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2632 (Protocol): To join, your game must run protocol 2632; cs160450 (Build): The server runs build 160450; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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
What is the way into Halo Test?
The manual route: launch Rust, F1, then client.connect 205.209.120.235:28080. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.