Rust StatisticsWorking papers on every public Rust server · 33,251 players now

Dragon Valley Test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 14d ago · 84.25.196.49:28015

Abstract

We describe the public Rust server Dragon Valley Test, reached at 84.25.196.49:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,459 of all servers, the top 62%. It last wiped 14d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/166% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,459top 62%
Last wipe14d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

The server stands in the top 62% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k7 Oct10 Oct13 Oct15 Oct18 Oct21 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap1.6 daysbetween real wipes
On rhythm33%of its recent wipes
Wipe-day peak2players, last three wipes
Wed 14 OctSat 10 OctThu 8 Oct
00.511.52+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 14 Oct, 09:3714d ago 1 – running 0
Sat 10 Oct, 08:0118d ago 1 – 4.1 d 2
Thu 8 Oct, 17:2320d ago 3 – 1.6 d 1
Wed 7 Oct, 19:4621d ago 3 – 0.9 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Custom map, no picture published
Figure 5: The map: Custom Map.
Table 4: The server's published settings.
Address84.25.196.49:28015
Region–
Max players16
Group limit8, the default
Wipe schedule–
Last wipe14 Oct 2026, 16:42 UTC
Hostname–
First seen7 Oct 2026
MapCustom Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and upcoming Rust wipes [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average54/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average133/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average76/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average24/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average6/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is Dragon Valley Test based?

No region is published by Dragon Valley Test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 84.25.196.49:28015.

A.2What is the online status and reliability of Dragon Valley Test?

At the present moment, Dragon Valley Test is offline; it was last seen 14 days 12 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 7 October 2026 by Rust Statistics.

A.3What is the Rust version for Dragon Valley Test?

The version of Rust on Dragon Valley Test is network protocol 2634 and build 167058, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.4When are wipes carried out on Dragon Valley Test?

No next wipe can be predicted for Dragon Valley Test since its wipes occur at irregular intervals. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 14 days 13 hours ago.

A.5How would you describe wipe day on Dragon Valley Test?

Recent wipes saw an average peak of 2 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.6What position does Dragon Valley Test occupy in the ranking of Rust servers?

Ranked by player hours across seven days, Dragon Valley Test holds #13,459, in the top 62% of all ranked servers.

A.7How would you characterise the player activity on Dragon Valley Test?

Dragon Valley Test is not online now; 14 days 12 hours have passed since it was last seen.

Tags and filters

A.8What do the tags associated with Dragon Valley Test signify?

Tags from Dragon Valley Test, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp16 (Max players): 16 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167058 (Build): The game build is 167058; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can Dragon Valley Test be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Dragon Valley Test: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.10What are the settings and rules that govern Dragon Valley Test?

Its name carries no gather rate for Dragon Valley Test. The group cap is 8 players, which is the default in the game. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC, Valve's anti-cheat, is enabled.

How to join

A.11How do you connect to Dragon Valley Test?

Enter client.connect 84.25.196.49:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp16,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp16Max players. 16 slots are available.
ts8Group limit. 8 per team, the value the game sets by default.
v2634Protocol. Your game must run protocol 2634 to connect.
cs167058Build. The game build is 167058.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.