Offline 157.85.95.130:28015 checked 25d ago
Dragonbile PVE
Connect
srv = rust.server("157.85.95.130:28016")
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, measured since 17 Sep. 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 best
Top 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 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 23 Sep, 18:09 UTC34d ago | 2 | NaN | running | 1 |
| 1 | Sun 13 Sep, 17:33 UTC44d ago | 2 | halved by day 3 | 10 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
3000 · seed 1031865839
- map
- Procedural Map
- size
- 3000
- seed
- 1031865839
Server
srv.info()- address
- 157.85.95.130:28015
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Sep 2026, 18:09 UTC
- hostname
- –
- first seen
- 13 Sep 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 · 164 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 130/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 31/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 141/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 47/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Dragonbile PVE rank?
Over the last seven days Dragonbile PVE sits at #16,006 on player hours, in the top 69% of ranked servers.
What population does Dragonbile PVE carry?
Offline now for Dragonbile PVE, with the last sample 25 days 21 hours ago.
Server data
What Rust version does Dragonbile PVE run?
Version Rust network protocol 2633 and build 165217 on Linux is reported by Dragonbile PVE. Steam updates your game for you, but the protocol must match to join.
How reliable is Dragonbile PVE, and is it up?
The latest sample has Dragonbile PVE offline, with a last sighting 25 days 21 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is Dragonbile PVE hosted?
There is no region published for Dragonbile PVE. Rust Data does not look up where the machine stands; it shows where a server says it is. 157.85.95.130:28015 is its address.
Settings and map
What rules and settings are recorded for Dragonbile PVE?
The name Dragonbile PVE carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Dragonbile PVE loaded?
Size 3,000, seed 1031865839: the procedural map on Dragonbile PVE, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
On what schedule does Dragonbile PVE wipe?
The record for Dragonbile PVE holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 34 days 2 hours ago, and that is the one in play.
On Dragonbile PVE, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 3 in the other cases.
Tags, lists
Which lists on Rust Data hold Dragonbile PVE, and which filters?
The Rust Data lists that Dragonbile PVE fits are: 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 Dragonbile PVE?
Read by the game's server browser, the tags Dragonbile PVE publishes are: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
How can I connect to Dragonbile PVE?
Enter client.connect 157.85.95.130:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.