Offline 77.251.65.27:28015 checked 6d ago
Dragon Valley Test
Connect
srv = rust.server("77.251.65.27: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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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 | Sat 17 Oct, 09:11 UTC12d ago | 1 | NaN | running | 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
- 77.251.65.27:28015
- region
- –
- max players
- 16
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 11:18 UTC
- hostname
- –
- first seen
- 17 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 · 150 on average | 14/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 35/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 8/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 36/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 136/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Dragon Valley Test rank?
Over the last seven days Dragon Valley Test sits at #15,284 on player hours, in the top 69% of ranked servers.
How many players does Dragon Valley Test hold at once?
Dragon Valley Test returns no live count at this refresh, having last been seen 6 days 16 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Dragon Valley Test on?
Rust network protocol 2635 and build 168909 on Windows is what Dragon Valley Test runs. Joining needs the same protocol on your game; Steam handles the update.
Is Dragon Valley Test up, and what does its uptime show?
Offline now for Dragon Valley Test, last seen 6 days 16 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. The first row Rust Data holds for it is dated 17 October 2026.
Which location does Dragon Valley Test run from?
For Dragon Valley Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 77.251.65.27:28015.
Map and rules
Which settings and rules does Dragon Valley Test run?
No gather rate appears in the name: Dragon Valley Test. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Wipe schedule
On what schedule does Dragon Valley Test wipe?
A rhythm cannot be read from the wipes of Dragon Valley Test on record, which are too few. 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 12 days 14 hours ago, and that is the one in play.
What is wipe day on Dragon Valley Test like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Dragon Valley Test appear among Rust Data lists and filters?
On Rust Data, Dragon Valley Test appears in these lists: Modded Rust servers. 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.
Which meanings do the tags on Dragon Valley Test hold?
The game's server browser reads these tags from Dragon Valley Test: gmrust (Game mode): Rust survival in its standard form; mp16 (Max players): 16 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Connecting
What is the way to join Dragon Valley Test?
The manual route: launch Rust, F1, then client.connect 77.251.65.27:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.