RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h58 Scan5 min
‹ All servers159.196.23.103:28015
Offline Full Queue Fresh wipe Wipe due No query

Adink Staging Test

Offline 159.196.23.103:28015 checked 6d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

10% full 7-day avg7-day peak
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 average1peak 1
Rank#10,914top 49%
Last wipe6d 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
15k10k15k20k12 Oct15 Oct18 Oct22 Oct25 Oct28 Oct

Top 49% 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 gap6.8 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 22 OctThu 15 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 01:31 UTC6d ago 1 – running 0
Thu 15 Oct, 05:44 UTC13d ago 1 – 6.8 days 0

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 timing

What should you expect from wipe day on Adink Staging Test?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Adink Staging Test wipe, and when?

To tell the rhythm of Adink Staging Test, 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 6 days 17 hours ago.

Tag meanings

How should you read the tags on Adink Staging Test?

Tags published by Adink Staging Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Adink Staging Test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Adink Staging Test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Player count

Where does Adink Staging Test sit in the rankings?

Ranking for Adink Staging Test: #10,914 on seven-day player hours, top 49% of all ranked servers.

What is the population on Adink Staging Test?

Status for Adink Staging Test: offline. Last seen 6 days 15 hours ago. Check: players over seven days. Average 1, peak 1.

Operator and location

Which location does Adink Staging Test run from?

No region comes from Adink Staging Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 159.196.23.103:28015.

What Rust version is Adink Staging Test on?

Reading: Adink Staging Test, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

Is Adink Staging Test up, and how often does it stay up?

Check: connection. Adink Staging Test is offline at this moment. Last contact was 6 days 15 hours ago. Uptime for the last 7 full days: 3 of 168 hours, or 2%. Check: first contact. Rust Metrics logged it on 12 October 2026.

Settings and map

What rules does Adink Staging Test enforce, and what are its settings?

Check: gather rate. The name Adink Staging Test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join Adink Staging Test?

To join: start Rust, press F1 and type client.connect 159.196.23.103:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.