Rust Data

rustdata.spaceservers213.202.205.23:21304.ipynb

Run all rust-data · live

‹ All servers

Online 213.202.205.23:21300 checked 13m ago

Dannabell@4Netplayers

moddedoxide

Connect

srv = rust.server("213.202.205.23:21304")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #4,201 # top 19%
last wipe 28d ago # no schedule published
next wipe 6d 23h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75120:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304020:0005:0014:0000:0009:0018: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
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 19% of all ranked servers. 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 6d 23h. # The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

inatkind
06d 23hThu 5 Nov, 19:00 UTCFW force wipe
134d 23hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 19:31 UTC FW28d ago 1 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

5000 · seed 523218427
Map of Dannabell@4Netplayers
map
Procedural Map
size
5000
seed
523218427
Open on RustMaps

Server

srv.info()
address
213.202.205.23:21300
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 19:31 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
0ShockRust | Blue | NoLimitno group limit · 151 on average94/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average127/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average153/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average63/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 90 on average185/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average348/350

Quick answers

From the figures on this page.

Player counts

How does Dannabell@4Netplayers compare in the rankings?

Player hours over seven days put Dannabell@4Netplayers at #4,201, in the top 19% of the ranked set.

How full does Dannabell@4Netplayers run?

The sample now reads 0 players for Dannabell@4Netplayers, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 20:00 UTC is the busiest, at 1 players.

Server facts

What does performance look like on Dannabell@4Netplayers?

The 48-hour average is 30 server fps, with a low of 28. Buildings, deployables and all else in the world took the count as high as 148,593 entities. A high of 3,925 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on Dannabell@4Netplayers?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Dannabell@4Netplayers. Joining needs the same protocol on your game; Steam handles the update.

Is Dannabell@4Netplayers up, and what does its uptime show?

Dannabell@4Netplayers reports itself online at the current refresh. A restart about 6 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is Dannabell@4Netplayers hosted?

For Dannabell@4Netplayers, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 213.202.205.23:21300.

Rules, settings, map

What rules and settings are recorded for Dannabell@4Netplayers?

You will not find a gather rate in the string Dannabell@4Netplayers. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.

What is the map on Dannabell@4Netplayers?

Dannabell@4Netplayers runs a procedural map of size 5,000 with seed 523218427, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

When does Dannabell@4Netplayers wipe, and on what schedule?

A single wipe each month, the force wipe, is all Dannabell@4Netplayers does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 28 days ago, and that is the one in play.

On Dannabell@4Netplayers, what happens on wipe day?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began.

Tags, lists

Which lists on Rust Data hold Dannabell@4Netplayers, and which filters?

These Rust Data lists include Dannabell@4Netplayers: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Dannabell@4Netplayers?

These tags are published by Dannabell@4Netplayers and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into Dannabell@4Netplayers?

Enter client.connect 213.202.205.23:21300 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

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

Game

gmvanilla
Game mode The mode is vanilla survival.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 102,609 players 11,866 servers online