ServerHub Test
Offline 171.217.41.32:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer 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 bestWipe 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- 132/500
- 127/100
- 187/225
- 75/700
- 10/200
- 22/1000
Quick answers
from the figures on this pageReset cycle
When does ServerHub Test wipe?
The rhythm of ServerHub Test's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 53 days 3 hours ago.
Lists and filters
Which tags does ServerHub Test carry, and what do they mean?
These are the tags ServerHub Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Build 163207; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does ServerHub Test appear in Rust Metrics lists and filters?
On Rust Metrics, ServerHub Test sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Occupancy
What position does ServerHub Test hold among Rust servers?
Ranking for ServerHub Test: #15,025 on seven-day player hours, top – of all ranked servers.
What player count does ServerHub Test carry?
Status for ServerHub Test: offline. Last seen 44 days 17 hours ago.
Server details
What location is ServerHub Test hosted in?
No region tag on ServerHub Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 171.217.41.32:28015.
What Rust version is ServerHub Test on?
Reading: ServerHub Test, Rust network protocol 2633 and build 163207, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is ServerHub Test, and is it online now?
ServerHub Test reports offline. The last reading came 44 days 17 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 14 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on ServerHub Test?
Check: gather rate. The name ServerHub Test does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.
What map is ServerHub Test on?
The game generates a procedural map for ServerHub Test.
Join
How can you get onto ServerHub Test?
Check: join. Open Rust, press F1, then enter client.connect 171.217.41.32:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.