Rust Server Analytics 53,198 players11,665 servers
All servers
Drill-through Server detail

Chagamaru test

Online EA 82.21.2.3:10278 checked 7m ago

Drill-through
FilterServeris Chagamaru test
Attributes
monthly wipes moddedcarbonpve
Last refreshed
Players now 0/ 45
7-day average 0 peak 1
Rank #9,200 top 41% · #451 in EA
Last wipe 26d ago monthly schedule
Next wipe 8d 9h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.250.50.75110:0019:0004:0014:0023:0008:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
010020030040010:0019:0004:0014:0023:0008: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
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 41% of all ranked servers, top 82% in EA. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 9h. The force wipe · high confidence

usual gap1.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

Coming wipes

InWhen, UTCKind
8d 9hThu 5 Nov, 19:00 UTCFW force wipe
36d 9hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Thu 1 OctThu 1 OctTue 29 Sep
00.511.52+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
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:03 UTC FW26d ago 0 – running 0
Thu 1 Oct, 12:48 UTC26d ago 1 – 0.3 days 1
Tue 29 Sep, 13:44 UTC28d ago 2 – 2 days 0
Tue 22 Sep, 08:01 UTC36d ago 2 halved by day 2 7.2 days 0
Mon 21 Sep, 13:34 UTC36d ago 2 – 0.8 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 EA · groups of 8+ · monthly · 35 on average 40 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 21 on average 23 / 88
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服 EA · groups of 8+ · monthly · 12 on average 12 / 100
【青岩-PVE服】原倍/萌新/突袭据点 EA · groups of 8+ · monthly · 11 on average 10 / 200
[JP]ちょっぴりHard-PvE RiSu Server EA · groups of 8+ · monthly · 11 on average 7 / 100
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 EA · groups of 16+ · monthly · 10 on average 10 / 100

Quick answers

from the figures on this page

Wipe data

When does Chagamaru test wipe?

The force wipe is the only wipe for Chagamaru test, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 26 days 12 hours ago the current world was made. A monthly wipe schedule is published in its tags.

On Chagamaru test, what happens on wipe day?

The average busiest count over recent wipes is 1 players. The highest player count on the latest wipe arrived 0 hours in. Above half that peak until the next wipe held in 0% of recent wipes. By day 2 it had fallen below half where the hold failed.

Server

In which region does Chagamaru test sit?

Its EA tag puts Chagamaru test in Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 82.21.2.3:10278.

What Rust build does Chagamaru test run?

Rust network protocol 2635 and build 168909 on Linux is the setup for Chagamaru test. Joining requires the same protocol on your game; Steam handles the update.

How reliable is Chagamaru test, and is it online now?

The current status of Chagamaru test is online. The uptime it reports puts the last restart at about 5 hours ago. 100% uptime over the last 7 full days, equal to 168 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.

What performance does Chagamaru test show?

Server fps averaged 167 over the last 48 hours, with a floor of 29. Entity count reached 117,363, covering buildings, deployables and the rest of the world. At its highest, memory use was 4,108 MB. A climbing entity count and low fps are the lag players perceive.

Lists and tags

What do Chagamaru test's tags stand for?

Tags from Chagamaru test, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp45 (Max players): 45 slots in total; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Build number 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^m (Monthly): The wipe cycle is monthly and follows Facepunch's force wipe; ^p (PvE): No fighting between players, with the world as the threat; ^z (Modded): Modded listing, where plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon; EA (East Asia): Its browser listing sits in East Asia. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On Rust Server Analytics, which lists and filters feature Chagamaru test?

The following Rust Server Analytics lists count Chagamaru test among their servers: Modded Rust servers: live data and PvE Rust servers by live population. These filters bring it up on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.

Player numbers

Against other Rust servers, how does Chagamaru test compare?

Chagamaru test holds #9,200 on seven-day player hours and #451 in Asia, inside the top 41% of the ranked field.

At what level does Chagamaru test run its population?

Of 45 slots, 0 are filled on Chagamaru test at this refresh. Seven-day figures: an average of 0 players and a peak of 1. Averaged over 48 hours, activity is highest at 13:00 UTC with 0 players.

Settings

How is Chagamaru test configured, and what rules apply?

Gather rate is not mentioned in the name of Chagamaru test. The game's default 8-player group limit is in force. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Carbon plugins are run. Anti-cheat status: VAC on.

The map on Chagamaru test: which one is it?

Chagamaru test uses a procedural map of size 4,750 with seed 2147483647, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Named map: Custom Map.

How to join

What is the way onto Chagamaru test?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 82.21.2.3:10278.

Server tags

what each one means

Published as mp45,ptrak,$r?,v2635,^z,^y,^m,EA,^p,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in the standard Rust format.
mp45
Max players 45 slots in total.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Build number 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code The region code is blank.

Wipe schedule

^m
Monthly The wipe cycle is monthly and follows Facepunch's force wipe.

Gameplay

^p
PvE No fighting between players, with the world as the threat.

Mods and access

^z
Modded Modded listing, where plugins or settings change the game.
^y
Carbon Plugin framework: Carbon.

Region

EA
East Asia Its browser listing sits in East Asia.

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.