RUST METRICSFlight deck · live data
Data live Servers11,824 Players75,694 Populated3,728 Fresh wipes 3 h230 Scan5 min
‹ All servers82.169.117.163:28021
Offline Full Queue Fresh wipe Wipe due No query

adhd/markprivebuildserver/testing

Offline 82.169.117.163:28021 checked 27d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#16,330top 69%
Last wipe40d agono schedule published
Next wipe–too few wipes 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 Sep23 Sep26 Sep2 Oct5 Oct8 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

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

usual gap4 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 19 SepTue 15 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 19 Sep, 12:34 UTC40d ago 3 – running 1
Tue 15 Sep, 13:43 UTC44d ago 2 held half 4 days 1

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

What happens on adhd/markprivebuildserver/testing when wipe day comes?

At their busiest, its recent wipes drew 2 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does adhd/markprivebuildserver/testing follow?

To tell the rhythm of adhd/markprivebuildserver/testing, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 40 days 1 hours ago.

Tags

How should you read the tags on adhd/markprivebuildserver/testing?

These are the tags adhd/markprivebuildserver/testing publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show adhd/markprivebuildserver/testing?

On Rust Metrics, adhd/markprivebuildserver/testing sits in these lists: Modded Rust servers, checked live and Build and creative servers. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does adhd/markprivebuildserver/testing hold among Rust servers?

Player hours over seven days put adhd/markprivebuildserver/testing at #16,330, in the top 69% of all ranked servers.

What is the population on adhd/markprivebuildserver/testing?

Reading for adhd/markprivebuildserver/testing: offline at this moment; last seen 27 days 21 hours ago.

Operator and location

Which location does adhd/markprivebuildserver/testing run from?

No region comes from adhd/markprivebuildserver/testing. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 82.169.117.163:28021.

What Rust version is adhd/markprivebuildserver/testing on?

Rust network protocol 2633 and build 163794 on Windows is the build adhd/markprivebuildserver/testing runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on adhd/markprivebuildserver/testing, and is it online?

Check: connection. adhd/markprivebuildserver/testing is offline at this moment. Last contact was 27 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What settings and rules apply on adhd/markprivebuildserver/testing?

Check: gather rate. The name adhd/markprivebuildserver/testing does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

What map is adhd/markprivebuildserver/testing on?

The game generates a procedural map for adhd/markprivebuildserver/testing.

Join

What do you do to join adhd/markprivebuildserver/testing?

Check: join. Open Rust, press F1, then enter client.connect 82.169.117.163:28021. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as 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.