RUST METRICSFlight deck · live data
Data live Servers11,748 Players63,000 Populated3,404 Fresh wipes 3 h200 Scan5 min
‹ All servers24.66.37.218:28015
Offline Full Queue Fresh wipe Wipe due No query

Dragon PvE - [5x|Bots|Events]

Offline 24.66.37.218:28015 checked 14d ago

5x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,156top 70%
Last wipe24d agobiweekly schedule
Next wipe3d 10hSun 1 Nov, 22:42 UTC
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep26 Sep3 Oct9 Oct16 Oct22 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Sunday 1 November, 22:42 UTC, in 3d 10h. 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

  1. WPT 1Sun 1 Nov, 22:42 UTC3d 10h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 7hFW
  3. WPT 3Sun 15 Nov, 22:42 UTC17d 10h
  4. WPT 4Sun 29 Nov, 22:42 UTC31d 10h
  5. WPT 5Thu 3 Dec, 19:00 UTC35d 7hFW

The first 48 hours of its last wipes

Sun 4 OctMon 21 SepSun 20 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 22:42 UTC24d ago 2 – running 1
Mon 21 Sep, 04:55 UTC38d ago 4 halved by day 7 13.7 days 0
Sun 20 Sep, 07:51 UTC39d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Dragon PvE - [5x|Bots|Events]?

At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 20 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 7 it fell below half when it didn't.

What wipe timing does Dragon PvE - [5x|Bots|Events] follow?

Its tag guides the prediction: too few of Dragon PvE - [5x|Bots|Events]'s wipes are on record to confirm its schedule. Sunday 1 November at 22:42 UTC is when its next wipe is due. The world it runs now was made 24 days 12 hours ago. The tags carry an every-two-weeks wipe schedule.

Tag meanings

How should you read the tags on Dragon PvE - [5x|Bots|Events]?

Check: tags. The game's server browser reads gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe schedule; ^k (Build server): Check: mode. Builds, for practising and designing bases; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; oxidation (Custom tag): A plugin or the owner set this tag; Rust does not ship it from Dragon PvE - [5x|Bots|Events]. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Who operates Dragon PvE - [5x|Bots|Events]?

Most likely the same operator runs both: Dragon PvE - [5x|Bots|Events] publishes a dragonpve.com hostname, and 1 other server we track does the same.

Where does Dragon PvE - [5x|Bots|Events] appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Dragon PvE - [5x|Bots|Events]: Best 5x Rust servers: live readings, Modded Rust servers, checked live and Build and creative servers. These filters bring it up 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.

Occupancy

What position does Dragon PvE - [5x|Bots|Events] hold among Rust servers?

Player hours over seven days put Dragon PvE - [5x|Bots|Events] at #15,156, in the top 70% of all ranked servers.

How full does Dragon PvE - [5x|Bots|Events] get?

Status for Dragon PvE - [5x|Bots|Events]: offline. Last seen 14 days 5 hours ago.

Server details

What location is Dragon PvE - [5x|Bots|Events] hosted in?

Reading: location. Dragon PvE - [5x|Bots|Events] gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 24.66.37.218:28015.

What Rust version is Dragon PvE - [5x|Bots|Events] on?

Reading: Dragon PvE - [5x|Bots|Events], Rust network protocol 2634 and build 167781, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is Dragon PvE - [5x|Bots|Events] up, and how often does it stay up?

Dragon PvE - [5x|Bots|Events] reports offline. The last reading came 14 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 20 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Dragon PvE - [5x|Bots|Events] enforce, and what are its settings?

Gather rate check: 5x. That comes from the name Dragon PvE - [5x|Bots|Events]. No limit is set beyond the default. Groups take up to 8 players. build & creative, no gathering; sandbox building instead — that is the game mode. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

What map is Dragon PvE - [5x|Bots|Events] on?

From seed 1413388568, the game generates the procedural map on Dragon PvE - [5x|Bots|Events]. Its size is 4,500. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto Dragon PvE - [5x|Bots|Events]?

Check: join. Open Rust, press F1, then enter client.connect 24.66.37.218:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/smDv2Sa.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^b,^k,gmvanilla,cs167781,ts8,^o^z,oxidation

Game

gmvanilla
Game mode The mode is vanilla survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Gameplay

^k
Build server Check: mode. Builds, for practising and designing bases.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Other

oxidation
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.