Station XX-13459 · no signal
Dragon Valley Test
Offline 84.25.196.49:28015 checked 13d ago
- Players now
- 1/ 16
- 6% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,459
- top 62%
- Last wipe
- 13d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 16 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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1.6 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 2players, 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 |
|---|---|---|---|---|---|---|
| Wed 14 Oct, 09:37 UTC14d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sat 10 Oct, 08:01 UTC18d ago | M0.0▼falling | 1 | – | – | 4.1 days | 2 |
| Thu 8 Oct, 17:23 UTC19d ago | M0.3▲rising | 3 | – | 1.6 days | 1 | |
| Wed 7 Oct, 19:46 UTC20d ago | M0.5▲rising | 3 | – | 0.9 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 pageMap and rules
Which settings and rules apply on Dragon Valley Test?
The name of Dragon Valley Test gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on Dragon Valley Test?
Dragon Valley Test is not responding at this moment and is offline, last seen 13 days 17 hours ago.
How does Dragon Valley Test rank against other Rust servers?
On player hours for the past week, Dragon Valley Test sits at #13,459, which puts it inside the top 62% of every ranked server.
Server details
How reliably does Dragon Valley Test stay online?
As recorded now, Dragon Valley Test is not reachable, the last contact having been 13 days 17 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 7 October 2026.
Which region does Dragon Valley Test run from?
A region is not published by Dragon Valley Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 84.25.196.49:28015.
Which Rust version is Dragon Valley Test running?
Dragon Valley Test is running Rust network protocol 2634 and build 167058 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Dragon Valley Test?
The recent wipes averaged a busiest count of 2 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Dragon Valley Test run its wipes?
There is no next wipe to predict at Dragon Valley Test, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 13 days 18 hours.
Tags
What do the server tags on Dragon Valley Test mean?
These are the tags Dragon Valley Test publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp16 (Max players): 16 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167058 (Build): It runs game build 167058; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Dragon Valley Test appear?
The Rust Server Trends lists that take in Dragon Valley Test are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
What steps get you onto Dragon Valley Test?
Enter client.connect 84.25.196.49:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.