Rust Server TrendsSeismic network · station log
Recording Stations11,751 Players55,890 Active3,402 Wipes · 3 h132 48 h

Station XX-3984 · recording

Dragon PvE - [5x|Bots|Events]

Online 70.75.201.189:28015 checked 11m ago

5x biweekly wipes moddedoxide
Connect
Players now
1/ 100
1% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 4
Rank
#3,984
top 18%
Last wipe
12d ago
biweekly schedule
Next wipe
7d 19h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-3984 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 100 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+1into Wed 03:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5200:0009:0018:0002:0011:0021:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020000:0009:0018:0002:0011:0021: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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

from its schedule tag

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

usual gap
6 daysbetween real wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 3

Coming wipes

  1. 7d 19hThu 5 Nov, 19:00 UTCFW
  2. 21d 1hThu 19 Nov, 01:11 UTC
  3. 35d 19hThu 3 Dec, 19:00 UTCFW

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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 22 Oct, 01:11 UTC6d ago M0.5rising 3 – running 0
Fri 16 Oct, 00:11 UTC12d ago M0.0rising 1 halved by day 3 6 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[PVE]AMIGOS X5 EU · groups of 10+ · 5x · biweekly · 1 on average
1/ 100
SEED RUST X5 | NOLIMIT | BOOST FPS | BUILD DEEP SEA | WIPE 27.1 EU · groups of 48+ · 5x · weekly · 2 on average
0/ 100
可爱-1000倍PVE-不掉-突袭-养殖-僵尸-无限耐久 EA · groups of 8+ · biweekly · 1 on average
0/ 100
177/ 999
189/ 999
38/ 150
Readings, in words

Quick answers

from the figures on this page

Server rules

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

Dragon PvE - [5x|Bots|Events] runs a procedural map of size 4,500 with seed 832328038, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

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

Going by its name, Dragon PvE - [5x|Bots|Events] runs 5x gather. Groups hold up to 8 players, which is the default for the game. It plays in build & creative mode, building in a sandbox, and no gathering. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on Dragon PvE - [5x|Bots|Events] right now?

A reading taken now shows 1 players on Dragon PvE - [5x|Bots|Events], which has 100 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 4. The busiest point in the last 48 hours came at 03:00 UTC, averaging 1 players.

How does Dragon PvE - [5x|Bots|Events] rank against other Rust servers?

Over the last seven days, Dragon PvE - [5x|Bots|Events] recorded enough player hours to reach #3,984 worldwide, placing it in the top 18% of all ranked servers.

Server details

How reliably does Dragon PvE - [5x|Bots|Events] stay online?

Dragon PvE - [5x|Bots|Events] is up at the moment. Its reported uptime points to a restart about 12 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. Its earliest appearance in the records of Rust Server Trends dates to 15 October 2026.

Does Dragon PvE - [5x|Bots|Events] hold a steady tick rate?

The 48-hour average is 90 server fps; 38 is the lowest observed. The world held up to 173,448 entities at its peak, buildings and deployables included. Memory use peaked at 5,888 MB. Low fps together with a growing entity count is what players experience as lag.

Where in the world is Dragon PvE - [5x|Bots|Events] hosted?

No region is published by Dragon PvE - [5x|Bots|Events]. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 70.75.201.189:28015.

What build of Rust does Dragon PvE - [5x|Bots|Events] use?

Rust network protocol 2635 and build 168909 on Linux is what Dragon PvE - [5x|Bots|Events] runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Dragon PvE - [5x|Bots|Events]?

2 players, on average, was the busiest crowd at its recent wipes. 42 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. It fell under half by day 3 in the wipes where it didn't hold.

How often does Dragon PvE - [5x|Bots|Events] wipe, and on which days?

Its schedule cannot be confirmed, as too few of Dragon PvE - [5x|Bots|Events]'s wipes are on record; the prediction follows its tag instead. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 12 days 23 hours. Every two weeks it wipes, according to the schedule in its tags.

Tags

What do the server tags on Dragon PvE - [5x|Bots|Events] mean?

Tags published by Dragon PvE - [5x|Bots|Events] and read by the game's server browser include gmvanilla (Game mode): You'll find vanilla survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): A wipe comes every second week; ^k (Build server): A place to design and practise bases; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; oxidation (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Dragon PvE - [5x|Bots|Events] appear?

You will find Dragon PvE - [5x|Bots|Events] on the following Rust Server Trends lists: 5x Rust servers, Modded Rust servers, tracked live and Rust build and creative servers, live. On the server list, the filters it matches are: 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.

Which person or group runs Dragon PvE - [5x|Bots|Events]?

Both Dragon PvE - [5x|Bots|Events] and 1 other server we track publish a dragonpve.com hostname, so one operator most likely runs them.

Join the server

What steps get you onto Dragon PvE - [5x|Bots|Events]?

Enter client.connect 70.75.201.189:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/smDv2Sa.

Instrument codes

Server tags

what each one means

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

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp100
Max players 100 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly A wipe comes every second week.

Gameplay

^k
Build server A place to design and practise bases.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

oxidation
Custom tag The owner or a plugin set this tag, and it's not one of Rust's standard tags.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.