Offline 167.114.158.11:28075 checked 39d ago
DO NOT JOIN - Hillside update test
Connect
srv = rust.server("167.114.158.11:28077")
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
Wipe schedule
srv.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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 167.114.158.11:28075
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Sep 2026, 00:28 UTC
- hostname
- –
- first seen
- 19 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 · 155 on average | 27/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 32/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 16/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 2/1000 |
Quick answers
From the figures on this page.
Population
What position does DO NOT JOIN - Hillside update test take in the server rankings?
Rank #15,450 on seven-day player hours for DO NOT JOIN - Hillside update test, within the top – of all ranked servers.
How full does DO NOT JOIN - Hillside update test run?
The current row shows DO NOT JOIN - Hillside update test offline; the last response was 39 days 23 hours ago.
Server data
What Rust version does DO NOT JOIN - Hillside update test run?
Rust network protocol 2633 and build 163207 on Linux is what DO NOT JOIN - Hillside update test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is DO NOT JOIN - Hillside update test, and is it online now?
The latest sample has DO NOT JOIN - Hillside update test offline, with a last sighting 39 days 23 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 19 September 2026.
In which location is DO NOT JOIN - Hillside update test hosted?
No region is published by DO NOT JOIN - Hillside update test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 167.114.158.11:28075.
Rules, settings, map
What rules and settings are recorded for DO NOT JOIN - Hillside update test?
No gather rate appears in the name: DO NOT JOIN - Hillside update test. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on DO NOT JOIN - Hillside update test?
The game generates its map: procedural, on DO NOT JOIN - Hillside update test.
Wipe data
On what schedule does DO NOT JOIN - Hillside update test wipe?
Too few wipes are on record for DO NOT JOIN - Hillside update test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 48 days 1 hours ago, and that is the one in play.
Tags and filters
Where does DO NOT JOIN - Hillside update test appear among Rust Data lists and filters?
The Rust Data lists that DO NOT JOIN - Hillside update test fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on DO NOT JOIN - Hillside update test?
These tags are published by DO NOT JOIN - Hillside update test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163207 (Build): Build number: 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to DO NOT JOIN - Hillside update test?
The manual route: launch Rust, F1, then client.connect 167.114.158.11:28075. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.