Skip to the page
Every Rust server graded on real, live numbers. 52,540 players on the roll · 11,716 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 28 October 2026 Pupil no. 157.85.95.130:28015
Name of server

Dragonbile PVE

RegisterAbsentOffline
Region–
Address157.85.95.130:28015
Last checked26d ago
moddedoxide
Launch Rust and join
Overall grade

Not there yet

26 out of 100, the average of 3 subjects

Players now 0/ 40 0% full
7-day average0peak –
Rank#16,006top 69%
Last wipe34d agono schedule published
Next wipe–too few wipes seen yet

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average unmarked No weekly average to mark yet.
Standingrank on player hours 31/ 100 Working its way up from the back of the class: #16,006 on player hours.
Uptimehours on the list, last 48 unmarked Not seen long enough to take a register.
Performanceserver fps, last 48 hours unmarked Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe 0/ 100 Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago 48/ 100 Slipped a little: down 768 places this week. Nothing a good wipe can't fix.

A term to build on. Strongest in momentum (D); wipes are the one to work on (F).

How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.

Progress through the term

Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k20 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Attendance: the wipe record

2 wipe days in the last 16 weeks

W wiped that day F the force wipe · today. From the wipes in the table below.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap10 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Wed 23 SepSun 13 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 23 Sep, 18:09 UTC34d ago 2 – running 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.

Similar servers

classmates: the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 163 on average
48 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10
EU · groups of 8+ · weekly · 128 on average
132 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 113 on average
64 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 87 on average
59 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 87 on average
13 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 83 on average
15 / 1000

Quick answers

from the figures on this page

Server details

In what location does Dragonbile PVE sit?

Dragonbile PVE leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 157.85.95.130:28015 is the address to use.

Is Dragonbile PVE up, and how steady is its uptime?

The server is down: Dragonbile PVE is offline now, with the last sighting 26 days 1 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.

What Rust version is Dragonbile PVE on?

You will find Dragonbile PVE on Rust network protocol 2633 and build 165217, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.

Resets

How frequently does Dragonbile PVE wipe its map?

The record holds too few of Dragonbile PVE's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 34 days 6 hours have passed since this world was made.

What happens on Dragonbile PVE when wipe day arrives?

Recent wipes have peaked at 2 players on average. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.

Player numbers

Where does Dragonbile PVE place in the wider field of Rust servers?

Over the last seven days, Dragonbile PVE has #16,006 for player hours, in the top 69% of all ranked servers.

What does the population on Dragonbile PVE look like?

Dragonbile PVE is offline at the moment; the last time it was seen was 26 days 1 hours ago.

Lists and filters

How should you read the tags on Dragonbile PVE?

The game's browser takes its cue from the tags Dragonbile PVE has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): Its slot count is 40; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.

Which Rust Server Score filters and lists feature Dragonbile PVE?

These Rust Server Score lists count Dragonbile PVE among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules and settings

Which rules does Dragonbile PVE enforce, and what are its settings?

You will find no gather rate in the name of Dragonbile PVE. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.

Which map is in play on Dragonbile PVE?

A procedural map of size 3,000 and seed 1031865839, generated by the game, is what Dragonbile PVE runs. A matching size and seed produce the same map, viewable on RustMaps from this page.

Connecting

How do you get onto Dragonbile PVE?

Enter client.connect 157.85.95.130:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.

Server tags

what each one means

Published as mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode This one runs plain Rust survival, with nothing altered.
mp40
Max players Its slot count is 40.
ts8
Group limit Teams are capped at 8, the game's standard setting.
v2633
Protocol The game protocol is 2633, so your game must match that version to join.
cs165217
Build Build number: 165217.
ptrak
Networking This is RakNet: the network layer Rust normally uses.
$r?
Region code A region code is not set here.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded Plugins or settings alter the game, so it sits under 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.