Station XX-15450 · no signal
DO NOT JOIN - Hillside update test
Offline 167.114.158.11:28075 checked 38d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,450
- no region published
- Last wipe
- 47d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 slots
- Motion · 24 h
- M –not enough readings
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 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on DO NOT JOIN - Hillside update test?
A procedural map runs on DO NOT JOIN - Hillside update test, generated by the game.
Which settings and rules apply on DO NOT JOIN - Hillside update test?
No gather rate appears in the name of DO NOT JOIN - Hillside update test. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on DO NOT JOIN - Hillside update test?
DO NOT JOIN - Hillside update test is not responding at this moment and is offline, last seen 38 days 23 hours ago.
How does DO NOT JOIN - Hillside update test rank against other Rust servers?
On player hours for the past week, DO NOT JOIN - Hillside update test sits at #15,450, which puts it inside the top – of every ranked server.
Server facts
How reliably does DO NOT JOIN - Hillside update test stay online?
DO NOT JOIN - Hillside update test is down at the moment; the last recorded contact was 38 days 23 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 19 September 2026 is when Rust Server Trends first recorded it.
Where in the world is DO NOT JOIN - Hillside update test hosted?
Nothing about a region comes from DO NOT JOIN - Hillside update test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 167.114.158.11:28075.
What build of Rust does DO NOT JOIN - Hillside update test use?
On Linux, DO NOT JOIN - Hillside update test runs Rust network protocol 2633 and build 163207. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does DO NOT JOIN - Hillside update test wipe, and on which days?
Too few wipes of DO NOT JOIN - Hillside update test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 47 days is how long the current world has been running.
Server tags
What do the server tags on DO NOT JOIN - Hillside update test mean?
The game's server browser reads the tags DO NOT JOIN - Hillside update test publishes: gmrust (Game mode): You'll find standard Rust survival here; mp2 (Max players): The server has 2 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163207 (Build): It runs game build 163207; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does DO NOT JOIN - Hillside update test appear?
You will find DO NOT JOIN - Hillside update test on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto DO NOT JOIN - Hillside update test?
You can connect by pressing F1 in Rust and typing client.connect 167.114.158.11:28075 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.