RUST METRICSFlight deck · live data
Data live Servers11,679 Players48,756 Populated3,222 Fresh wipes 3 h131 Scan5 min
‹ All servers167.114.158.11:28075
Offline Full Queue Fresh wipe Wipe due No query

DO NOT JOIN - Hillside update test

Offline 167.114.158.11:28075 checked 38d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,450no region published
Last wipe47d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
PLAN

Wipe schedule

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

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

When does DO NOT JOIN - Hillside update test wipe?

The rhythm of DO NOT JOIN - Hillside update test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 47 days ago.

Lists and filters

Which tags does DO NOT JOIN - Hillside update test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Build 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from DO NOT JOIN - Hillside update test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does DO NOT JOIN - Hillside update test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring DO NOT JOIN - Hillside update test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

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

Player hours over seven days put DO NOT JOIN - Hillside update test at #15,450, in the top – of all ranked servers.

What player count does DO NOT JOIN - Hillside update test carry?

DO NOT JOIN - Hillside update test is not responding; status offline, last seen 38 days 22 hours ago.

Server details

What location is DO NOT JOIN - Hillside update test hosted in?

Reading: location. DO NOT JOIN - Hillside update test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 167.114.158.11:28075.

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

Version check: Rust network protocol 2633 and build 163207 on Linux, run by DO NOT JOIN - Hillside update test. Matching protocol is required to join. Let Steam update your game.

What is the uptime on DO NOT JOIN - Hillside update test, and is it online?

Check: connection. DO NOT JOIN - Hillside update test is offline at this moment. Last contact was 38 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Map and rules

What rules does DO NOT JOIN - Hillside update test enforce, and what are its settings?

No gather rate appears in the name: DO NOT JOIN - Hillside update test. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on DO NOT JOIN - Hillside update test?

Procedural map on DO NOT JOIN - Hillside update test, made by the game's generator.

How to join

What do you do to join DO NOT JOIN - Hillside update test?

Press F1 in Rust and enter client.connect 167.114.158.11:28075. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players 2 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163207
Build Build 163207.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.