Rust Server TrendsSeismic network · station log
Recording Stations11,668 Players34,317 Active2,844 Wipes · 3 h86 48 h

Station XX-15490 · no signal

Diamond Blue TEST

Offline 46.19.66.6:28015 checked 39d ago

weekly wipes moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,490
top 69%
Last wipe
39d ago
weekly schedule
Next wipe
2d 16h
Sat 31 Oct, 20:12 UTC
Seismic record · station XX-15490 · 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 19 Sep. 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
15k10k15k20k20 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

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

Expected events

Wipe schedule

Next wipe Saturday 31 October, 20:12 UTC, in 2d 16h. Weekly: 7 days after its last wipe

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
134/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
38/ 225
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
3/ 200
[NA] Willjum's Solo Only | Thursday Wipes NA · groups of 8+ · weekly · 26 on average
16/ 100
[EU] Willjum's Solo Only | Thursday Wipes EU · groups of 8+ · weekly · 26 on average
2/ 175
QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 EA · groups of 20+ · weekly · 24 on average
30/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Diamond Blue TEST?

Generated by the game, the map on Diamond Blue TEST is procedural, size 2,500 with seed 87521200. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Diamond Blue TEST?

The name of Diamond Blue TEST gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on Diamond Blue TEST right now?

Diamond Blue TEST is not responding at this moment and is offline, last seen 39 days 6 hours ago.

How does Diamond Blue TEST rank against other Rust servers?

The last seven days of player hours place Diamond Blue TEST at #15,490, in the top 69% of all ranked servers.

Operator and location

How reliably does Diamond Blue TEST stay online?

As recorded now, Diamond Blue TEST is not reachable, the last contact having been 39 days 6 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 19 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does Diamond Blue TEST run from?

A region is not published by Diamond Blue TEST. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 46.19.66.6:28015 is the address it uses.

What build of Rust does Diamond Blue TEST use?

Rust network protocol 2633 and build 164530 on Windows is what Diamond Blue TEST runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

On what timetable does Diamond Blue TEST run its wipes?

From weekly: 7 days after its last wipe the next wipe of Diamond Blue TEST is estimated. The date of its next wipe is Saturday 31 October at 20:12 UTC. 39 days 7 hours is how long the current world has been running. The tags it publishes carry a weekly wipe schedule.

Lists and tags

What do the server tags on Diamond Blue TEST mean?

The game's server browser reads the tags Diamond Blue TEST publishes: gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^w (Weekly): The server wipes every week; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 Diamond Blue TEST appear?

These Rust Server Trends lists include Diamond Blue TEST: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.

Join the server

What steps get you onto Diamond Blue TEST?

You can connect by pressing F1 in Rust and typing client.connect 46.19.66.6:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,^w,gmvanilla,cs164530,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla mode.
mp50
Max players 50 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs164530
Build The game build is 164530.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^w
Weekly The server wipes every week.

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.

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.