RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h42 Scan5 min
‹ All servers70.75.201.189:28015
Online Full Queue Fresh wipe Wipe due No query

Dragon PvE - [5x|Bots|Events]

Online 70.75.201.189:28015 checked 2h ago

5x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 17:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 86 SERVER FPS

Server fps

48 h low 38 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 168,671 ×1000

Entities

48 h range 139,407–174,813 · memory 3,863 MB
1239 ET SINCE RESTART 07:02

Uptime

7 h 2 min since its last restart, at the last reading
7-day average1peak 4
Rank#3,974top 18%
Last wipe12d agobiweekly schedule
Next wipe7d 23hThu 5 Nov, 19:00 UTC FW
Memory3,863MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5220:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020020:0005:0014:0023:0008:0017:00

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k15 Oct18 Oct20 Oct23 Oct25 Oct28 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h. The force wipe · high confidence

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

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 23hFW
  2. WPT 2Thu 19 Nov, 01:11 UTC21d 5h
  3. WPT 3Thu 3 Dec, 19:00 UTC35d 23hFW

The first 48 hours of its last wipes

Thu 22 OctFri 16 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 42 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 01:11 UTC6d ago 3 – running 0
Fri 16 Oct, 00:11 UTC12d ago 1 halved by day 3 6 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

Reset cycle

What happens on Dragon PvE - [5x|Bots|Events] when wipe day comes?

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

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

The prediction follows its tag, because too few of Dragon PvE - [5x|Bots|Events]'s wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 12 days 19 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Tags

Which tags does Dragon PvE - [5x|Bots|Events] carry, and what do they mean?

These are the tags Dragon PvE - [5x|Bots|Events] publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^k (Build server): Check: mode. Builds, for practising and designing bases; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; oxidation (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which operator is behind Dragon PvE - [5x|Bots|Events]?

Check: operator. Dragon PvE - [5x|Bots|Events] publishes a dragonpve.com hostname, and so does 1 other server we track. Same operator, most likely.

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

On Rust Metrics, Dragon PvE - [5x|Bots|Events] sits in these lists: 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; Last wipe: In the last 2 weeks; Gather rate: 5x.

Player count

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

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

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

0 of 100 slots are filled on Dragon PvE - [5x|Bots|Events] right now. Check: players over seven days. Average 1, peak 4. The last 48 hours peaked at 21:00 UTC, averaging 2 players at that hour.

Server

Which location does Dragon PvE - [5x|Bots|Events] run from?

Reading: location. Dragon PvE - [5x|Bots|Events] gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 70.75.201.189:28015.

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

Version check: Rust network protocol 2635 and build 168909 on Linux, run by Dragon PvE - [5x|Bots|Events]. Matching protocol is required to join. Let Steam update your game.

Is performance on Dragon PvE - [5x|Bots|Events] within range?

Over the last 48 hours the average was 90 server fps; the floor was 38. Check: entities. The peak was 174,813, counting buildings, deployables and the rest of the world. Reading: 5,888 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on Dragon PvE - [5x|Bots|Events], and is it online?

Reading: online. Dragon PvE - [5x|Bots|Events] answers right now. Reading: uptime. About 7 hours ago it restarted, on its own count. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 15 October 2026.

Rules and settings

What settings and rules apply on Dragon PvE - [5x|Bots|Events]?

The name carries the rate: 5x gather on Dragon PvE - [5x|Bots|Events]. The group cap is 8 players, which is the default in the game. Mode check gives build & creative; no gathering; sandbox building instead. The server browser lists it as Modded, where plugins or settings change how the game plays. 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?

Size 4,500 and seed 832328038: the game generates the procedural map on Dragon PvE - [5x|Bots|Events] from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

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

Check: join. Open Rust, press F1, then enter client.connect 70.75.201.189:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/smDv2Sa is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode The mode is vanilla survival.
mp100
Max players 100 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

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 Modded: plugins or settings depart from the stock 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.