Offline 78.190.60.166:28025 checked 27d ago
RustHook Test
Connect
srv = rust.server("78.190.60.166:27017")
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. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:35 UTC FW27d ago | 0 | NaN | running | 0 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 78.190.60.166:28025
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:35 UTC
- hostname
- –
- first seen
- 23 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 | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 176/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 70/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 90 on average | 211/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
How does RustHook Test compare in the rankings?
Player hours over seven days put RustHook Test at #15,920, in the top 70% of the ranked set.
What population does RustHook Test carry?
The current row shows RustHook Test offline; the last response was 27 days 4 hours ago.
Server facts
What Rust version does RustHook Test run?
The build is Rust network protocol 2634 and build 166494 on Linux, run by RustHook Test. Steam updates your game for you, but the protocol must match to join.
How reliable is RustHook Test, and is it online now?
The latest sample has RustHook Test offline, with a last sighting 27 days 4 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 23 September 2026.
Which location does RustHook Test run from?
No region is published by RustHook Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 78.190.60.166:28025 is its address.
Map and rules
What rules and settings are recorded for RustHook Test?
The name RustHook Test carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
Which map has RustHook Test loaded?
The game generates its map: procedural, on RustHook Test.
Wipes and dates
On what schedule does RustHook Test wipe?
The only wipe RustHook Test takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 27 days 23 hours ago.
On RustHook Test, what happens on wipe day?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold RustHook Test, and which filters?
These Rust Data lists include RustHook Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on RustHook Test?
The game's server browser reads these tags from RustHook Test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Build number: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into RustHook Test?
Enter client.connect 78.190.60.166:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.