Rust Data

rustdata.spaceservers78.46.62.251:28027.ipynb

Run all rust-data · live

‹ All servers

Offline EU 78.46.62.251:28025 checked 16d ago

STAGING_DG3x_test

quad monthly wipes vanillamoddedoxide

Connect

srv = rust.server("78.46.62.251:28027")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,503 # top 71% · #2566 in EU
last wipe 27d ago # monthly schedule
next wipe 7d 12h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k23 Sep28 Sep3 Oct8 Oct14 Oct19 Oct

Top 71% of all ranked servers, top 87% in EU, and #610 of the quad servers (top 77%). Ranked on player hours over the last seven days.

Wipe schedule · force wipes only

srv.wipe_schedule()

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

usual gap1.2 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak0players, last three wipes

Coming wipes

inatkind
07d 12hThu 5 Nov, 19:00 UTCFW force wipe
135d 12hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Thu 1 OctWed 30 SepSun 27 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 16:24 UTC27d ago 0 NaN running 0
1 Wed 30 Sep, 15:53 UTC28d ago 0 NaN 1 days 0
2 Sun 27 Sep, 16:59 UTC31d ago 0 NaN 3 days 0
3 Sat 26 Sep, 11:24 UTC32d ago 0 NaN 1.2 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.

display(srv.map, srv.info())

Map

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
78.46.62.251:28025
region
EU
max players
10
group limit
quad
wipe schedule
monthly
last wipe
1 Oct 2026, 17:36 UTC
hostname
–
first seen
23 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Persona#1 |Для Новичков| х2EU · quad · monthly · 3 on average0/200
1Aqua Rust | Server has migratedEU · quad · monthly · 2 on average0/100
2[EU] TideRust - Solo/Duo/Trio/Quad | Monthly |No BP WipesEU · quad · monthly · 128 on average58/250
3[TR/EU] VATAN | Solo/Duo/Trio/Quad | Yeni başlayanlar içinEU · quad · monthly · 84 on average61/350
4RustForNoobs.com | Solo Duo Trio Quad | Monthly | EUEU · quad · monthly · 10 on average2/200
5Noobs 4 Real | No Pros, No Sweats, Just Noobs, Solo/Duo!EU · quad · monthly · 3 on average0/100

Quick answers

From the figures on this page.

Player counts

What position does STAGING_DG3x_test take in the server rankings?

Player hours over the last seven days: #15,503 for STAGING_DG3x_test, #2,566 in Europe, within the top 71% of the ranked set. Within the quad group, its rank is #610.

How many players does STAGING_DG3x_test hold at once?

Offline now for STAGING_DG3x_test, with the last sample 16 days 12 hours ago.

Server facts

Which Rust version is STAGING_DG3x_test on?

Version Rust network protocol 2634 and build 166494 on Windows is reported by STAGING_DG3x_test. Joining needs the same protocol on your game; Steam handles the update.

How reliable is STAGING_DG3x_test, and is it up?

STAGING_DG3x_test is offline at this refresh; the last response came 16 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 23 September 2026.

Which location does STAGING_DG3x_test run from?

In Europe, STAGING_DG3x_test lists itself, using the EU tag. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 78.46.62.251:28025.

Map and rules

Which rules apply on STAGING_DG3x_test, and what settings?

The name STAGING_DG3x_test carries no gather rate. quad sets the cap: 4 players per group. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Its own label is vanilla: facepunch's stock game, with rates, kits and rules untouched. Anti-cheat status: VAC on.

Wipe schedule

When does STAGING_DG3x_test wipe, and how often?

Once a month STAGING_DG3x_test wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 27 days 12 hours ago. The tags list wipes as monthly.

On STAGING_DG3x_test, what happens on wipe day?

Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.

Tags, lists

Which Rust Data filters and lists contain STAGING_DG3x_test?

The Rust Data lists that STAGING_DG3x_test fits are: EU Rust servers and Modded Rust servers. Under these filters on the server list, it is listed: Region: Europe; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Monthly.

How should you read the server tags on STAGING_DG3x_test?

The game's server browser reads these tags from STAGING_DG3x_test: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts4 (Group limit): Team size tops out at 4; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): Europe is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join STAGING_DG3x_test?

In Rust, F1 opens the console: type client.connect 78.46.62.251:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,^m,^v,EU,gmrust,cs166494,ts4,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts4
Group limit Team size tops out at 4.
v2634
Protocol To join, your game must run protocol 2634.
cs166494
Build Build number: 166494.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Difficulty

^v
Vanilla Facepunch's stock game, with rates, kits and rules untouched.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

EU
Europe Europe is its listing in the server browser.

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.

Rust Data 33,251 players 11,613 servers online