HSA
Offline 88.135.119.165:28015 checked 1d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avg7-day peakServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 54% of all ranked servers. Ranked on player hours over the last seven days.
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| Wiped | Peak | Crowd | Lasted | Players 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 297/300
- 275/250
- 24/250
- 21/250
- 37/100
- 122/200
Quick answers
from the figures on this pageWipe schedule
What wipe timing does HSA follow?
Its rhythm cannot be told from the wipes of HSA on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 15 days 18 hours ago the current world was made.
Tag meanings
How should you read the tags on HSA?
Tags published by HSA, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): 15 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does HSA appear in Rust Metrics lists and filters?
On Rust Metrics, HSA sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What position does HSA hold among Rust servers?
Ranking for HSA: #12,071 on seven-day player hours, top 54% of all ranked servers.
What is the population on HSA?
Status for HSA: offline. Last seen 41 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Check: 48-hour peak. 14:00 UTC, 1 players on average.
Server details
Where does HSA sit?
No region comes from HSA. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 88.135.119.165:28015.
What Rust version is HSA on?
Reading: HSA, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is HSA, and is it online now?
HSA reports offline. The last reading came 41 hours ago. Reading: 0% uptime over the last 1 full day. It was up 0 of 24 hours. The first sighting on Rust Metrics was 27 October 2026.
Rules and settings
How is HSA configured, and what rules are in force?
No gather rate appears in the name: HSA. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on HSA?
Check: map. Procedural, generated by the game, on HSA.
Connection
What do you do to join HSA?
To join: start Rust, press F1 and type client.connect 88.135.119.165:28015. Or press Launch Rust here and Steam opens the game and connects you.