Rust Server TrendsSeismic network · station log
Recording Stations11,794 Players80,292 Active3,570 Wipes · 3 h260 48 h

Station XX-15276 · no signal

Rust BF2 - Dragon Valley NL

Offline 185.228.82.15:28895 checked 2d ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,276
top 69%
Last wipe
2d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15276 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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 9 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
15k10k15k20k9 Oct13 Oct17 Oct21 Oct25 Oct29 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
9.1 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
2players, last three wipes
crowd held
0%else halves by day 1

The first 48 hours of its last wipes

Tue 27 OctSat 10 OctFri 9 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 27 Oct, 17:54 UTC2d ago M0.0steady 0 – – running 0
Sat 10 Oct, 12:13 UTC19d ago M0.5rising 3 halved by day 1 17.2 days 0
Fri 9 Oct, 14:41 UTC20d ago M0.0rising 3 – 0.9 days 2

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
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
131/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 120 on average
87/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average
34/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 92 on average
88/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
309/ 350
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
11/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Rust BF2 - Dragon Valley NL?

Rust BF2 - Dragon Valley NL runs a procedural map of size 3,000 with seed 1, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on Rust BF2 - Dragon Valley NL?

The name of Rust BF2 - Dragon Valley NL gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on Rust BF2 - Dragon Valley NL?

No players are recorded on Rust BF2 - Dragon Valley NL at this moment; it is offline, and the last sighting was 2 days 4 hours ago. Averaged across the last seven days, the population was 0 players.

How does Rust BF2 - Dragon Valley NL rank against other Rust servers?

Over the last seven days, Rust BF2 - Dragon Valley NL recorded enough player hours to reach #15,276 worldwide, placing it in the top 69% of all ranked servers.

Operator and location

How reliably does Rust BF2 - Dragon Valley NL stay online?

No contact with Rust BF2 - Dragon Valley NL right now, and the last recorded contact was 2 days 4 hours ago. 117 of 168 hours in the last 7 full days were up time, 70% of the total. 9 October 2026 is when Rust Server Trends first recorded it.

Which region does Rust BF2 - Dragon Valley NL run from?

The name of Rust BF2 - Dragon Valley NL points to Europe, even though it publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 185.228.82.15:28895 is the address it uses.

What build of Rust does Rust BF2 - Dragon Valley NL use?

Rust network protocol 2635 and build 168909 on Linux is what Rust BF2 - Dragon Valley NL runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on Rust BF2 - Dragon Valley NL?

The recent wipes averaged a busiest count of 2 players. The peak on the most recent wipe came 1 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.

On what timetable does Rust BF2 - Dragon Valley NL run its wipes?

There is no next wipe to predict at Rust BF2 - Dragon Valley NL, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 2 days 4 hours.

Server tags

What do the server tags on Rust BF2 - Dragon Valley NL mean?

These are the tags Rust BF2 - Dragon Valley NL publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; 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): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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 Rust BF2 - Dragon Valley NL appear?

You will find Rust BF2 - Dragon Valley NL on the following Rust Server Trends lists: EU Rust servers and Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Connecting

How do you connect to Rust BF2 - Dragon Valley NL?

To join, enter client.connect 185.228.82.15:28895 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
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 No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it 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.

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.