Rust Data

rustdata.spaceservers20.169.53.49:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 20.169.53.49:28015 checked 2d ago

Takaro Dev

Connect

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

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,348 # top 69%
last wipe 2d ago # no schedule published
next wipe – # no wipe seen yet

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
15k10k15k20k26 Oct27 Oct28 Oct

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

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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
20.169.53.49:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 01:24 UTC
hostname
–
first seen
26 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 553 on average548/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average357/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 297 on average44/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average37/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 272 on average118/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average128/300

Quick answers

From the figures on this page.

Population

How does Takaro Dev compare in the rankings?

Player hours over seven days put Takaro Dev at #15,348, in the top 69% of the ranked set.

What population does Takaro Dev carry?

Offline now for Takaro Dev, with the last sample 2 days 19 hours ago. Over the last seven days it averaged 0 players.

Server data

Which Rust version is Takaro Dev on?

Rust network protocol 2635 and build 168909 on Linux is what Takaro Dev runs. Steam updates your game for you, but the protocol must match to join.

Is Takaro Dev up, and what does its uptime show?

Takaro Dev is offline at this refresh; the last response came 2 days 19 hours ago. Over the last 1 full day the hours up number 0 of 24, 0%. The first row Rust Data holds for it is dated 26 October 2026.

Where does Takaro Dev sit?

No region is published by Takaro Dev. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 20.169.53.49:28015.

Map and rules

Which rules apply on Takaro Dev, and what settings?

You will not find a gather rate in the string Takaro Dev. 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. Community is its browser category. Anti-cheat status: VAC off.

Which map has Takaro Dev selected?

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

Wipes and dates

When does Takaro Dev wipe, and how often?

Too few wipes are on record for Takaro Dev to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 2 days 19 hours ago, and that is the one in play.

Tags, lists

Where does Takaro Dev appear among Rust Data lists and filters?

These Rust Data lists include Takaro Dev: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Which meanings do the tags on Takaro Dev hold?

The game's server browser reads these tags from Takaro Dev: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

How can I connect to Takaro Dev?

The manual route: launch Rust, F1, then client.connect 20.169.53.49:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

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 73,970 players 11,800 servers online