Offline 84.25.196.49:28015 checked 14d ago
Dragon Valley Test
Connect
srv = rust.server("84.25.196.49:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 09:37 UTC14d ago | 1 | NaN | running | 0 |
| 1 | Sat 10 Oct, 08:01 UTC18d ago | 1 | NaN | 4.1 days | 2 |
| 2 | Thu 8 Oct, 17:23 UTC20d ago | 3 | NaN | 1.6 days | 1 |
| 3 | Wed 7 Oct, 19:46 UTC21d ago | 3 | NaN | 0.9 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.
display(srv.map, srv.info())Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 84.25.196.49:28015
- region
- –
- max players
- 16
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 16:42 UTC
- hostname
- –
- first seen
- 7 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 132/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 102/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 32/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 29/1000 |
Quick answers
From the figures on this page.
Population
What position does Dragon Valley Test take in the server rankings?
Player hours over seven days put Dragon Valley Test at #13,459, in the top 62% of the ranked set.
How full does Dragon Valley Test run?
The current row shows Dragon Valley Test offline; the last response was 14 days 3 hours ago.
Server data
What Rust version does Dragon Valley Test run?
The build is Rust network protocol 2634 and build 167058 on Windows, run by Dragon Valley Test. The protocol has to match before you can join, and Steam does the updating.
Is Dragon Valley Test up, and what does its uptime show?
The latest sample has Dragon Valley Test offline, with a last sighting 14 days 3 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 7 October 2026.
Where does Dragon Valley Test sit?
There is no region published for Dragon Valley Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 84.25.196.49:28015 is its address.
Rules, settings, map
Which settings and rules does Dragon Valley Test run?
No gather rate appears in the name: Dragon Valley Test. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Wipes and dates
On what schedule does Dragon Valley Test wipe?
Irregular wipe times on Dragon Valley Test leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 14 days 4 hours ago, and that is the one in play.
What is wipe day on Dragon Valley Test like?
Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does Dragon Valley Test appear among Rust Data lists and filters?
These Rust Data lists include Dragon Valley Test: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Dragon Valley Test?
The game's server browser reads these tags from Dragon Valley Test: gmrust (Game mode): Survival play, standard Rust; mp16 (Max players): The server lists 16 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): The server runs build 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join Dragon Valley Test?
In Rust, F1 opens the console: type client.connect 84.25.196.49:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.