Rust Data

rustdata.spaceservers148.251.2.84:30016.ipynb

Run all rust-data · live

‹ All servers

Online 148.251.2.84:30015 checked 11m ago

[GER]DuKs TESTSERVER

moddedoxide

Connect

srv = rust.server("148.251.2.84:30016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,351 # top 69%
last wipe 19d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123406:0015:0000:0009:0019:0004:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304006:0015:0000:0009:0019:0004: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 17 Sep. 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
15k10k15k20k20 Sep28 Sep5 Oct14 Oct21 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

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 Sat 10 Oct, 03:05 UTC19d ago 0 NaN running 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

4000 · seed 1
Map of [GER]DuKs TESTSERVER
map
Custom Map
size
4000
seed
1
custom map
download

Server

srv.info()
address
148.251.2.84:30015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
10 Oct 2026, 03:05 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average129/100
1RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average54/225
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average17/700
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average2/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average5/1000
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 79 on average64/700

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does [GER]DuKs TESTSERVER rank?

Over the last seven days [GER]DuKs TESTSERVER sits at #15,351 on player hours, in the top 69% of ranked servers.

What population does [GER]DuKs TESTSERVER carry?

Current row: 0 players on [GER]DuKs TESTSERVER, against 10 slots. Over the last seven days it averaged 0 players.

Server facts

What does performance look like on [GER]DuKs TESTSERVER?

The 48-hour average is 38 server fps, with a low of 9. Entity numbers reached 92,108, and that includes buildings, deployables and the rest. A high of 2,603 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does [GER]DuKs TESTSERVER run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by [GER]DuKs TESTSERVER. Joining needs the same protocol on your game; Steam handles the update.

How reliable is [GER]DuKs TESTSERVER, and is it up?

Online is the state at the latest refresh for [GER]DuKs TESTSERVER. The uptime it reports puts the last restart about 23 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

Which location does [GER]DuKs TESTSERVER run from?

No region tag is published by [GER]DuKs TESTSERVER, though its name points to Europe. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 148.251.2.84:30015.

Map and rules

Which rules apply on [GER]DuKs TESTSERVER, and what settings?

You will not find a gather rate in the string [GER]DuKs TESTSERVER. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has [GER]DuKs TESTSERVER loaded?

Custom map, 4,000, run by [GER]DuKs TESTSERVER; the file is published, so download it here.

Wipes and dates

On what schedule does [GER]DuKs TESTSERVER wipe?

The record for [GER]DuKs TESTSERVER holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 19 days 2 hours ago, and that is the one in play.

On [GER]DuKs TESTSERVER, what happens on wipe day?

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Lists and tags

Where does [GER]DuKs TESTSERVER appear among Rust Data lists and filters?

These Rust Data lists include [GER]DuKs TESTSERVER: EU Rust servers and Modded Rust servers. 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.

Which meanings do the tags on [GER]DuKs TESTSERVER hold?

These tags are published by [GER]DuKs TESTSERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; rustmaps (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

What is the way to join [GER]DuKs TESTSERVER?

In Rust, F1 opens the console: type client.connect 148.251.2.84:30015. Launch Rust on this page does the same by opening the game through Steam and connecting. https://rust.duks-gaming.com is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

Other

rustmaps
Custom tag This tag comes from the owner or a plugin, not from Rust itself.

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 31,668 players 11,619 servers online