Station XX-10914 · no signal
Adink Staging Test
Offline 159.196.23.103:28015 checked 6d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 1
- peak 1
- Rank
- #10,914
- top 49%
- Last wipe
- 6d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 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 bestTop 49% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 6.8 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 01:31 UTC6d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 15 Oct, 05:44 UTC13d ago | M0.0▲rising | 1 | – | 6.8 days | 0 |
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 settings and rules apply on Adink Staging Test?
You will find no gather rate in the name of Adink Staging Test. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on Adink Staging Test?
A reading taken now finds Adink Staging Test offline; the most recent activity was 6 days 14 hours ago. The seven-day average is 1 players, with a peak of 1.
How does Adink Staging Test rank against other Rust servers?
Over the last seven days, Adink Staging Test recorded enough player hours to reach #10,914 worldwide, placing it in the top 49% of all ranked servers.
Server facts
How reliably does Adink Staging Test stay online?
Adink Staging Test is down at the moment; the last recorded contact was 6 days 14 hours ago. It was up 2% of the time across the last 7 full days: 3 of 168 hours. On 12 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Adink Staging Test run from?
A region is not published by Adink Staging Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 159.196.23.103:28015 is the address it uses.
What build of Rust does Adink Staging Test use?
On Windows, Adink Staging Test runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Adink Staging Test?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Adink Staging Test run its wipes?
On record so far are too few of Adink Staging Test's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 6 days 16 hours.
Server tags
What do the server tags on Adink Staging Test mean?
Tags published by Adink Staging Test and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 Adink Staging Test appear?
You will find Adink Staging Test on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How to join
How do you connect to Adink Staging Test?
You can connect by pressing F1 in Rust and typing client.connect 159.196.23.103:28015 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.