ServerHub Test
Offline 118.114.92.60:28015 checked 12d ago
Players
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 71% 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
- 17/ 100
- 245/ 400
- 182/ 225
- 134/ 100
- 296/ 1000
- 21/ 700
Quick answers
Tags and listings
Where does ServerHub Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include ServerHub Test: Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on ServerHub Test?
gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): It holds 10 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166652 (Build): The build number is 166652; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): Plugins are handled by Carbon — that is the tag list ServerHub Test puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What location is ServerHub Test in?
ServerHub Test does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 118.114.92.60:28015.
How reliable is ServerHub Test?
ServerHub Test is down at the moment; it was last up 12 days 23 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 4 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for ServerHub Test?
Rust network protocol 2634 and build 166652 is what ServerHub Test runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe schedule
What schedule does ServerHub Test follow for wipes?
The wipes recorded for ServerHub Test are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world you are on now was created 14 days 23 hours.
Settings and map
Which rules and settings is ServerHub Test running?
Its name does not state a gather rate for ServerHub Test. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Carbon. VAC, Valve's anti-cheat, is enabled.
What's the map on ServerHub Test?
ServerHub Test uses a game-generated procedural map.
Player stats
How many players are on ServerHub Test?
The last sighting of ServerHub Test was 12 days 23 hours ago; it is offline right now.
What position does ServerHub Test hold in the server rankings?
For player hours in the last seven days, ServerHub Test ranks #15,966, within the top 71% of ranked servers.
Join info
How do you get into ServerHub Test?
Open Rust and press F1, then type client.connect 118.114.92.60:28015. Alternatively, click Launch Rust on this page to join via Steam.