Working its way up from the back of the class: #15,156 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
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
20/ 100
F
Lost ground: down 9,118 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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 five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
W······
······W
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Sunday 1 November, 22:42 UTC, in 3d 21h.
Its biweekly schedule tag · low confidence
usual gap7.3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 7
Coming wipes
3d 21hSun 1 Nov, 22:42 UTC
7d 18hThu 5 Nov, 19:00 UTCFW
17d 21hSun 15 Nov, 22:42 UTC
31d 21hSun 29 Nov, 22:42 UTC
35d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 4 OctMon 21 SepSun 20 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 20 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 22:42 UTC24d ago
2
–
running
1
Mon 21 Sep, 04:55 UTC37d ago
4
halved by day 7
13.7 days
0
Sun 20 Sep, 07:51 UTC38d ago
1
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Dragon PvE - [5x|Bots|Events] based in?
No region is published for Dragon PvE - [5x|Bots|Events]. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 24.66.37.218:28015.
Is Dragon PvE - [5x|Bots|Events] up, and how steady is its uptime?
You cannot join now: Dragon PvE - [5x|Bots|Events] is offline, last seen 13 days 18 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Dragon PvE - [5x|Bots|Events] running?
You will find Dragon PvE - [5x|Bots|Events] on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Dragon PvE - [5x|Bots|Events] reset?
Its tag sets the prediction, as the record holds too few of Dragon PvE - [5x|Bots|Events]'s wipes to confirm its schedule. Expect the next wipe on Sunday 1 November at 22:42 UTC. 24 days 1 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
What happens on Dragon PvE - [5x|Bots|Events] when wipe day arrives?
The average peak on its recent wipes was 2 players. Peak numbers came 20 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 7.
Player count
What position does Dragon PvE - [5x|Bots|Events] hold in the rankings?
Over the last seven days, Dragon PvE - [5x|Bots|Events] has #15,156 for player hours, in the top 70% of all ranked servers.
How many players does Dragon PvE - [5x|Bots|Events] usually have?
Dragon PvE - [5x|Bots|Events] is offline at the moment; the last time it was seen was 13 days 18 hours ago.
Tags
What do Dragon PvE - [5x|Bots|Events]'s tags stand for?
The game's browser takes its cue from the tags Dragon PvE - [5x|Bots|Events] has set: gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^k (Build server): Bases can be designed and practised here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; oxidation (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. 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.
Who is behind Dragon PvE - [5x|Bots|Events]?
1 other server we track also publishes a dragonpve.com hostname, as Dragon PvE - [5x|Bots|Events] does, so the same operator most likely runs them all.
Which Rust Server Score filters and lists feature Dragon PvE - [5x|Bots|Events]?
These Rust Server Score lists count Dragon PvE - [5x|Bots|Events] among them: 5x Rust servers, graded, Modded Rust servers, graded and Rust build and creative servers. It shows under the following filters on the server list: Type: Modded; Server tag: Biweekly ^b, Build server ^k, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Gather rate: 5x.
Server rules
Which rules does Dragon PvE - [5x|Bots|Events] enforce, and what are its settings?
The name of Dragon PvE - [5x|Bots|Events] points to a 5x gather rate. The group limit stays at the game's default of 8 players. It runs build & creative, no gathering, just sandbox building. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Dragon PvE - [5x|Bots|Events]?
A procedural map of size 4,500 and seed 1413388568, generated by the game, is what Dragon PvE - [5x|Bots|Events] runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to Dragon PvE - [5x|Bots|Events]?
Enter client.connect 24.66.37.218:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/smDv2Sa.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^b,^k,gmvanilla,cs167781,ts8,^o^z,oxidation
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^k
Build serverBases can be designed and practised here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Other
oxidation
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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.
A term to build on. Strongest in standing (F); wipes are the one to work on (F).