StatusLive Servers online11,829 Players89,289 Populated4,008 Wiped · 3 h58 Interval5 min Date28 OCT 2026

DWG RG-S9178Server sheetchecked 2h ago

Chagamaru test

Online EA 82.21.2.3:10278 checked 2h ago

monthly wipes moddedcarbonpve
Connect
Players now 0/ 45 0% full
7-day average0peak 1
Rank#9,178top 41% · #444 in EA
Last wipe26d agomonthly schedule
Next wipe7d 23hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
00.250.50.75120:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Fig. 1Players on Chagamaru test
Fig. 2

Server performance

010020030040020:0005:0014:0023:0008:0017: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h. 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

  1. 7d 23hThu 5 Nov, 19:00 UTCFW
  2. 35d 23hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Thu 1 OctThu 1 OctTue 29 Sep
00.511.52+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:03 UTC FW26d ago 0 – running 0
Thu 1 Oct, 12:48 UTC27d ago 1 – 0.3 days 1
Tue 29 Sep, 13:44 UTC29d 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 UTC37d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 35 on average
35 / 100
02
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 21 on average
24 / 88
03
[熊猫PVE]修仙升级/召唤/据点/10月新档正式服EA · groups of 8+ · monthly · 12 on average
13 / 100
04
[JP]ちょっぴりHard-PvE RiSu ServerEA · groups of 8+ · monthly · 11 on average
15 / 100
05
【青岩-PVE服】原倍/萌新/突袭据点EA · groups of 8+ · monthly · 11 on average
8 / 200
06
新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简EA · groups of 16+ · monthly · 10 on average
10 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

What uptime is recorded for Chagamaru test, and is it up?

Right now, Chagamaru test is recorded as online. The uptime it reports puts the last restart at about 59 minutes ago. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 13 September 2026.

How does Chagamaru test perform, as measured?

The last 48 hours give an average of 175 server fps and a floor of 95. Counted at its highest: 117,811 entities, buildings, deployables and the rest of the world included. Memory use peaked at 4,167 MB. Players feel low fps and a climbing entity count as lag.

What location is recorded for Chagamaru test?

With its EA tag, Chagamaru test lists itself in Asia. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 82.21.2.3:10278.

On which Rust version is Chagamaru test running?

Rust network protocol 2635 and build 168909 on Linux: that is what Chagamaru test runs. To join, your game must be on the same protocol; Steam handles the update.

Player data

How many players are plotted on Chagamaru test?

0 of 45 slots on Chagamaru test are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 1. The 48-hour peak falls at 13:00 UTC, averaging 0 players.

What rank has been recorded for Chagamaru test?

Across seven days, player hours give Chagamaru test #9,178 globally and #444 in Asia, a top 41% position among ranked servers.

Schedules

On Chagamaru test, what does the data show for wipe day?

The recent wipes averaged a busiest count of 1 players. At 0 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 0% of its recent wipes stayed above half that peak. On the wipes where it did not hold, the crowd dropped below half by day 2.

On Chagamaru test, when do wipes occur?

The force wipe is the only wipe at Chagamaru test, once a month. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. The current world has been in use since 26 days 22 hours ago. A wipe every month is the schedule its tags set out.

Map and rules

Which settings does Chagamaru test run, and what rules?

The name of Chagamaru test records no gather rate. The group limit is 8 players, the game's default. It runs the pve game mode, no fighting other players. The server browser lists it under Modded: plugins or settings change the game. Carbon plugins are run on it. VAC is on: that is Valve's anti-cheat.

On which map is Chagamaru test played?

Size 4,750 with seed 2147483647: that is the procedural map Chagamaru test runs, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The map is named as follows: Custom Map.

Tags

On Rust Graphs, which lists and filters contain Chagamaru test?

On Rust Graphs, Chagamaru test is placed in these lists: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: 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.

Which meaning is attached to each tag on Chagamaru test?

gmrust (Game mode): Survival in standard Rust style; mp45 (Max players): 45 player slots; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^m (Monthly): Monthly wipes, on Facepunch's force wipe; ^p (PvE): No player combat: the threat comes from the world; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Plugin framework: Carbon; EA (East Asia): The browser's listing places it under East Asia are the tags Chagamaru test publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Connect

How is Chagamaru test joined?

In Rust, press F1 and type client.connect 82.21.2.3:10278 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

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 standard Rust style.
mp45
Max players 45 player slots.
ts8
Group limit The default team size of 8 applies.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^m
Monthly Monthly wipes, on Facepunch's force wipe.

Gameplay

^p
PvE No player combat: the threat comes from the world.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon Plugin framework: Carbon.

Region

EA
East Asia The browser's listing places it under 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.

KeyTag string decoded