Statistical profileOnline
Halo Test
205.209.120.235:28080 checked 7m ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,276
top 69%
Last wipe
84d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- There were 0 players on it, 0% of its 50 slots.
- It ranks #15,276 of all ranked servers, the top 69%, on player hours over the last seven days.
- Its current map went up 84d ago.
2. Players
Figure 1: Players on Halo Test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of Halo Test
3500 · seed 664382915
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 3500 |
| Seed | 664382915 |
8. Server characteristics
Table 3: Characteristics of Halo Test
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 150 on average | 36 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 65 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 24 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 73 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 281 / 310 |
10. Quick answers
From the figures on this page.
Wipe details
This release records the wipe timetable for Halo Test: what is it?
The rhythm of Halo Test's wipes cannot yet be told: too few are on record. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. 84 days have passed since this world was made.
Server details
Is Halo Test up, and how well has it held up?
Halo Test is online at the time of this release. The uptime it reports puts the last restart at about 2 days 10 hours ago. 167 of 168 hours on across the last 7 full days gives an uptime of 99%. First recorded by Rust Census on 13 September 2026.
How well does Halo Test perform?
Average server fps over the last 48 hours was 139, with a low of 74. The world carried up to 65,850 entities, including buildings, deployables and all else. The peak memory use recorded was 2,828 MB. Lag, as players feel it, comes from low fps and a climbing entity count.
Which location does Halo Test run from?
No region is published by Halo Test. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. At 205.209.120.235:28080 it is addressed.
On which Rust version does Halo Test operate?
This release lists Halo Test on Rust network protocol 2632 and build 160450, running on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Player counts
What population has been recorded on Halo Test?
At counting time Halo Test recorded 0 players across 50 slots. Averaged across seven days, the count is 0 players.
In the rankings of Rust servers, where is Halo Test placed?
For seven-day player hours, Halo Test is ranked #15,276, placing it in the top 69% of all ranked servers.
Tags, lists
Where does Halo Test appear among the Rust Census lists and filters?
The Rust Census lists that Halo Test fits are: Modded Rust servers, counted. Under these filters it comes up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
The tags on Halo Test: what do they indicate?
These are the tags Halo Test publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp50 (Max players): Slots: 50; ts8 (Group limit): This is the game default: 8 to a team; v2632 (Protocol): To connect, your game version must match protocol 2632; cs160450 (Build): Game build: 160450; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. At the top of this page you will find the tags for current players, queue and world creation time.
Settings and map
Which map has been recorded for Halo Test?
Halo Test runs a procedural map of size 3,500 with seed 664382915, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page.
What settings and rules have been listed for Halo Test?
The name of Halo Test carries no gather rate. 8 players is the group limit, the game's default. survival is the game mode recorded, the standard game: gather, build, raid. Fighting other players and raiding are allowed. The server browser lists it under Modded: plugins or settings alter the game. Plugins on it number Oxide. The server runs VAC, Valve's anti-cheat.
Connecting
What is the way to join Halo Test?
Enter client.connect 205.209.120.235:28080 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp50,ptrak,$r?,v2632,gmrust,cs160450,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp50 | Max players Slots: 50. |
ts8 | Group limit This is the game default: 8 to a team. |
v2632 | Protocol To connect, your game version must match protocol 2632. |
cs160450 | Build Game build: 160450. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.