Rust PopulationField survey · Rust servers
Observing 33,246 players 11,665 servers 2,811 with someone on 81 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 9,165EAfirst seen 13 Sep 2026

Chagamaru test

Online EA 82.21.2.3:10278 checked 10m ago

monthly wipes moddedcarbonpve

Measurements

Players now
0/ 45
0% full
7-day average
0
peak 1
Rank
#9,165
top 41% · #443 in EA
Last wipe
27d ago
monthly schedule
Next wipe
7d 15h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

AveragePeak
00.250.50.75104:0013:0022:0007:0016:0002:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

010020030040004:0013:0022:0007:0016:0002: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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Obs. 4 · the wipe cycle

Wipe schedule

force wipes only

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

1.4 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 2

Coming wipes

7d 15h
Thu 5 Nov, 19:00 UTC
FW
35d 15h
Thu 3 Dec, 19:00 UTC
FW

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.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:03 UTC FW27d 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.

Field questions

Quick answers

from the figures on this page

Player counts

How does Chagamaru test rank against other Rust servers?

Chagamaru test ranks #9,165 on seven-day player hours, #443 in Asia, and sits in the top 41% of all ranked servers.

How busy is Chagamaru test?

The count reads 0 players on Chagamaru test, which has 45 slots. Seven days of counting give an average of 0 players and a peak of 1. Look at the last 48 hours and 13:00 UTC stands out: it averaged 0 players.

Lists and tags

What do the server tags on Chagamaru test mean?

The game's server browser reads the tags Chagamaru test publishes: gmrust (Game mode): Survival in the standard Rust style; mp45 (Max players): 45 slots are available; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): This server has no region code; ^m (Monthly): This server wipes once a month, at the same time as Facepunch's force wipe; ^p (PvE): Players do not fight each other; the world supplies the danger; ^z (Modded): Plugins or settings change the game; it is listed under Modded; ^y (Carbon): The plugin framework Carbon runs on this server; EA (East Asia): Its place in the server browser is under East Asia. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include Chagamaru test?

Chagamaru test appears among the Rust Population lists that follow: Modded Rust servers, counted and PvE servers, counted. These are the filters it appears under when you browse the 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.

Wipe notes

What does wipe day look like on Chagamaru test?

Across its recent wipes the busiest crowds averaged 1 players. 0 hours after the latest wipe the crowd peaked. In 0% of recent wipes, half the peak was held until the next wipe. The crowd dropped below half by day 2 when it did not hold.

What is the wipe schedule on Chagamaru test?

The force wipe is the only wipe Chagamaru test takes, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world it runs now dates from 27 days 6 hours ago. In its tags a monthly wipe schedule is published.

Settings

Which map does Chagamaru test run?

The map on Chagamaru test is procedural, made by the game at size 4,750 from seed 2147483647. Size and seed together fix the map, so you can view it on RustMaps from this page. You will see the map named Custom Map.

What are the rules and settings on Chagamaru test?

The name tells you nothing about gather rates: Chagamaru test states none. The group limit is 8 players, which is the default. pve is what it runs, no player combat. Modded is its browser category: plugins or settings change the game. You will find Carbon running as plugins. The anti-cheat VAC from Valve is enabled.

About the server

Which version of Rust does Chagamaru test run?

On Linux, Chagamaru test runs Rust network protocol 2635 and build 168909. Steam updates your game automatically, but you need the same protocol to join.

Does Chagamaru test run smoothly?

It ran at 168 server fps on average over the last 48 hours, and never went below 63. Entities peaked at 118,100, including buildings, deployables and everything else. Up to 4,167 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.

Is Chagamaru test online, and how reliable is it?

You will find Chagamaru test online now. Judging by the uptime it reports, the last restart was about 5 hours ago. Over the last 7 full days, 167 of 168 hours were online, or 99%. The first sighting by Rust Population was on 13 September 2026.

Where is Chagamaru test located?

With its EA tag, Chagamaru test places itself in Asia. Rust Population does not look up where the machine stands; it shows where the server says it is. You will find it at 82.21.2.3:10278.

How to join

How do I join Chagamaru test?

Open the console with F1 in Rust and enter client.connect 82.21.2.3:10278. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

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 style.
mp45
Max players 45 slots are available.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code This server has no region code.

Wipe schedule

^m
Monthly This server wipes once a month, at the same time as Facepunch's force wipe.

Gameplay

^p
PvE Players do not fight each other; the world supplies the danger.

Mods and access

^z
Modded Plugins or settings change the game; it is listed under Modded.
^y
Carbon The plugin framework Carbon runs on this server.

Region

EA
East Asia Its place in the server browser is 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.