Rust Data

rustdata.spaceservers183.77.206.189:23431.ipynb

Run all rust-data · live

‹ All servers

Online 183.77.206.189:23429 checked 10m ago

Chirakari Members Server

moddedoxide

Connect

srv = rust.server("183.77.206.189:23431")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123407:0016:0002:0010:0019:0004:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608007:0016:0002:0010: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 Sep6 Oct14 Oct22 Oct30 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 Fri 9 Oct, 01:24 UTC21d 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

4250 · seed 1652930283
Map of Chirakari Members Server
map
Procedural Map
size
4250
seed
1652930283
Open on RustMaps

Server

srv.info()
address
183.77.206.189:23429
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
9 Oct 2026, 01:24 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 average36/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average125/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 123 on average54/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average9/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average42/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average40/200

Quick answers

From the figures on this page.

Population data

How does Chirakari Members Server compare in the rankings?

Player hours over seven days put Chirakari Members Server at #15,273, in the top 69% of the ranked set.

How many players does Chirakari Members Server hold at once?

Chirakari Members Server reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players.

Server data

How well does Chirakari Members Server perform?

Server fps over the last 48 hours averages 57; the floor is 52. The entity count peaked at 105,238, covering buildings, deployables and the rest of the world. A high of 4,616 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on Chirakari Members Server?

Version Rust network protocol 2634 and build 167231 on Windows is reported by Chirakari Members Server. The protocol has to match before you can join, and Steam does the updating.

Is Chirakari Members Server up, and what does its uptime show?

The current sample puts Chirakari Members Server online. A restart about 8 days 13 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Chirakari Members Server sit?

No region is published by Chirakari Members Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 183.77.206.189:23429 is its address.

Rules, settings, map

Which rules apply on Chirakari Members Server, and what settings?

You will not find a gather rate in the string Chirakari Members Server. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has Chirakari Members Server selected?

The game generates the map on Chirakari Members Server: procedural, size 4,250, seed 1652930283. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does Chirakari Members Server wipe?

The record for Chirakari Members Server holds too few wipes to show a rhythm. 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 21 days 4 hours ago.

On Chirakari Members Server, what happens on wipe day?

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

Tags and filters

Where does Chirakari Members Server appear among Rust Data lists and filters?

The Rust Data lists that Chirakari Members Server fits are: 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 Chirakari Members Server?

The game's server browser reads these tags from Chirakari Members Server: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167231 (Build): Build number: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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

How can I connect to Chirakari Members Server?

Enter client.connect 183.77.206.189:23429 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?,v2634,gmrust,cs167231,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167231
Build Build number: 167231.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: 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 40,013 players 11,602 servers online