Rust Data

rustdata.spaceservers83.134.186.18:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 83.134.186.18:28015 checked 3d ago

Takaro Dev Rust

moddedcarbon

Connect

srv = rust.server("83.134.186.18:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #13,692 # top 62%
last wipe 9d ago # no schedule published
next wipe – # no rhythm it keeps

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
15k10k15k20k21 Sep28 Sep7 Oct15 Oct22 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

usual gap9.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Mon 19 OctThu 1 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 19 Oct, 14:10 UTC9d ago 1 NaN running 0
1 Thu 1 Oct, 18:30 UTC FW27d ago 1 halved by day 1 17.8 days 1
2 Thu 1 Oct, 09:58 UTC28d ago 1 NaN 0.4 days 0
3 Mon 21 Sep, 20:12 UTC37d ago 0 NaN 9.6 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
83.134.186.18:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
19 Oct 2026, 14:10 UTC
hostname
–
first seen
21 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 · 149 on average130/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average192/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average73/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average10/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average17/1000

Quick answers

From the figures on this page.

Population

How does Takaro Dev Rust compare in the rankings?

Player hours over seven days put Takaro Dev Rust at #13,692, in the top 62% of the ranked set.

What population does Takaro Dev Rust carry?

The current row shows Takaro Dev Rust offline; the last response was 3 days 8 hours ago. Over the last seven days it averaged 0 players and peaked at 1.

Server data

What is the Rust version on Takaro Dev Rust?

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

How reliable is Takaro Dev Rust, and is it online now?

Takaro Dev Rust is offline at this refresh; the last response came 3 days 8 hours ago. Over the last 7 full days the hours up number 99 of 168, 59%. Its earliest recorded date in Rust Data is 21 September 2026.

Where does Takaro Dev Rust sit?

No region is published by Takaro Dev Rust. 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 83.134.186.18:28015.

Settings and map

Which settings and rules does Takaro Dev Rust run?

You will not find a gather rate in the string Takaro Dev Rust. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. The VAC field reads off.

Which map has Takaro Dev Rust selected?

Takaro Dev Rust runs a procedural map, which the game generates.

Wipe data

On what schedule does Takaro Dev Rust wipe?

No next wipe can be predicted for Takaro Dev Rust, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 9 days 20 hours ago.

What is wipe day on Takaro Dev Rust like?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 1.

Tags and filters

Which lists on Rust Data hold Takaro Dev Rust, and which filters?

The Rust Data lists that Takaro Dev Rust fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on Takaro Dev Rust hold?

These tags are published by Takaro Dev Rust and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join Takaro Dev Rust?

Enter client.connect 83.134.186.18:28015 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,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon The plugin framework in use is Carbon.

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 54,561 players 11,701 servers online