Rust Data LabData lab · live
Live readings Servers11,811 Players70,411 Populated3,728 Fresh wipes · 3h130 Sampled every 5 min

Element card · group Modded · atomic number 15,450, its rank

DO NOT JOIN - Hillside update test

Offline 167.114.158.11:28075 checked 38d ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 2 0% full Room to join
7-day average0peak –
Rank · atomic number#15,450no region published
Last wipe46d agono schedule published
Next wipe–no wipe seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
This server has not answered a direct query in the last 48 hours.

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
Reaction kinetics

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
  1. 1 Sh ShockRust | Bl… 104
    ShockRust | Blue | NoLimit no group limit · 164 on average 104/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 135
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 135/ 100
  3. 3 Re RETRO RUST #1 … 113
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 112 on average 113/ 225
  4. 4 Ru RustSpain.com … 29
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 29/ 200
  5. 5 Ru 404 RUST 2Х|ДЛ… 105
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 86 on average 105/ 700
  6. 6 Ru 404 RUST 2Х|ДЛ… 33
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average 33/ 1,000

Quick answers

from the figures on this page

Settings and map

What map is in play on DO NOT JOIN - Hillside update test?

Generated by the game, the map on DO NOT JOIN - Hillside update test is procedural.

What rules has DO NOT JOIN - Hillside update test set, and what settings are in force?

Nothing in the name of DO NOT JOIN - Hillside update test gives a gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins are running on it. The VAC anti-cheat from Valve is enabled.

About the server

What region hosts DO NOT JOIN - Hillside update test?

There is no region on record for DO NOT JOIN - Hillside update test. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. You will find it at 167.114.158.11:28075.

Which Rust version is DO NOT JOIN - Hillside update test on?

Rust network protocol 2633 and build 163207 on Linux is what DO NOT JOIN - Hillside update test uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How reliably does DO NOT JOIN - Hillside update test stay online?

Currently offline, DO NOT JOIN - Hillside update test was last seen 38 days 19 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. On 19 September 2026, Rust Data Lab saw it for the first time.

Wipe schedule

How often does a wipe happen on DO NOT JOIN - Hillside update test, and at what time?

Too few wipes are on record for DO NOT JOIN - Hillside update test to reveal a rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 46 days 21 hours ago.

Lists and tags

What should you understand from the tags DO NOT JOIN - Hillside update test carries?

The game's server browser reads the tags DO NOT JOIN - Hillside update test publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): It has 2 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game must match protocol 2633; cs163207 (Build): Build number: 163207; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does DO NOT JOIN - Hillside update test come up?

The Rust Data Lab lists that include DO NOT JOIN - Hillside update test are: Modded Rust servers, measured. You can find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does DO NOT JOIN - Hillside update test hold among Rust servers?

Player hours over the last week put DO NOT JOIN - Hillside update test at #15,450, inside the top – of ranked servers.

How many players does DO NOT JOIN - Hillside update test have at the moment?

DO NOT JOIN - Hillside update test is offline at the moment; the last sighting was 38 days 19 hours ago.

Getting on

What steps get you onto DO NOT JOIN - Hillside update test?

You can connect by pressing F1 in Rust and entering client.connect 167.114.158.11:28075, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

Published as mp2,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp2
Max players It has 2 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2633
Protocol To join, your game must match protocol 2633.
cs163207
Build Build number: 163207.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code The region field is left blank.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.