Rust StatisticsWorking papers on every public Rust server · 102,212 players now

Chirakari Members Server

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 183.77.206.189:23429

Abstract

We describe the public Rust server Chirakari Members Server, reached at 183.77.206.189:23429. At the last check it held 0 of 10 places, against a seven-day mean of 01. It ranks #15,327 of all servers, the top 69%. It last wiped 20d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,327top 69%
Last wipe20d agono schedule published
Next wipe3–too few wipes seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123418:0003:0012:0022:0007:0016:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
02040608018:0003:0012:0022:0007:0016:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

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

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak0players, last three wipes
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 9 Oct, 01:2420d ago 0 – 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Chirakari Members Server
Figure 5: The map: Procedural Map, size 4250, seed 1652930283. Open on RustMaps.
Table 4: The server's published settings.
Address183.77.206.189:23429
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe9 Oct 2026, 01:24 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4250
Seed1652930283

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and upcoming Rust wipes [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average151/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average125/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average187/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average96/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 88 on average234/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average348/350

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of Chirakari Members Server smooth?

The server fps averaged 57 over the last 48 hours, never dropping below 49. The highest number of entities it carried was 105,238, comprising buildings, deployables and all other objects. The peak memory usage was 4,421 MB. Players experience lag when fps is low and the entity count is rising.

A.2What is the location of Chirakari Members Server?

No region is published by Chirakari Members Server. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 183.77.206.189:23429 is its address.

A.3What is the reliability of Chirakari Members Server, and is it online?

At the present moment, Chirakari Members Server is online. The uptime it reports indicates a restart about 8 days 1 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. It was first observed on 13 September 2026 by Rust Statistics.

A.4What is the Rust version for Chirakari Members Server?

The version of Rust on Chirakari Members Server is network protocol 2634 and build 167231, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.5What schedule does Chirakari Members Server follow for wipes?

Too few wipes by Chirakari Members Server have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 20 days 16 hours ago.

A.6How would you describe wipe day on Chirakari Members Server?

Across its recent wipes, the average peak population was 0 players. The peak on the latest wipe came 0 hours after it began.

Population

A.7What position does Chirakari Members Server occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Chirakari Members Server at #15,327, within the top 69% of ranked servers.

A.8At what level does Chirakari Members Server operate in terms of players?

On Chirakari Members Server, 0 of the 10 slots are occupied at present. The seven-day average for this server is 0 players.

Tags, lists

A.9How should the tags on Chirakari Members Server be interpreted?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp10 (Max players): The slot count is 10; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167231 (Build): This server runs game build 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded, which Chirakari Members Server publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can Chirakari Members Server be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Chirakari Members Server fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.11What are the settings and rules that govern Chirakari Members Server?

The name of Chirakari Members Server states no gather rate. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.

A.12What is the map for Chirakari Members Server?

Generated by the game from seed 1652930283, the procedural map on Chirakari Members Server measures 4,250. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

Connection

A.13How do you connect to Chirakari Members Server?

Press F1 inside Rust to open the console and enter client.connect 183.77.206.189:23429. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2634,gmrust,cs167231,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp10Max players. The slot count is 10.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Your game must run protocol 2634 to connect.
cs167231Build. This server runs game build 167231.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.