RUST METRICSFlight deck · live data
Data live Servers11,713 Players47,275 Populated3,205 Fresh wipes 3 h100 Scan5 min
‹ All servers20.169.53.49:28015
Offline Full Queue Fresh wipe Wipe due No query

Takaro Dev

Offline 20.169.53.49:28015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,349top 69%
Last wipe2d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 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.

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does Takaro Dev follow?

To tell the rhythm of Takaro Dev, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 2 days 23 hours ago the current world was made.

Lists and filters

How should you read the tags on Takaro Dev?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Takaro Dev. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Takaro Dev appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Takaro Dev: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Occupancy

What position does Takaro Dev hold among Rust servers?

Ranking for Takaro Dev: #15,349 on seven-day player hours, top 69% of all ranked servers.

What player count does Takaro Dev carry?

Status for Takaro Dev: offline. Last seen 2 days 23 hours ago. Check: player average. 0 over the last seven days.

Server details

What location is Takaro Dev hosted in?

No region comes from Takaro Dev. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 20.169.53.49:28015.

What Rust version is Takaro Dev on?

Rust network protocol 2635 and build 168909 on Linux is the build Takaro Dev runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Takaro Dev, and is it online?

Check: connection. Takaro Dev is offline at this moment. Last contact was 2 days 23 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. Reading: first seen 26 October 2026, recorded by Rust Metrics.

Rules and settings

How is Takaro Dev configured, and what rules are in force?

Check: gather rate. The name Takaro Dev does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC off, Valve's system.

What map is Takaro Dev on?

Check: map. Procedural, generated by the game, on Takaro Dev.

How to join

How can you get onto Takaro Dev?

Check: join. Open Rust, press F1, then enter client.connect 20.169.53.49:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.