On the class lists: D (47), with population over 48 hours and no performance mark.
Players now0/ 450% full
7-day average0peak 1
Rank#9,134top 41% · #438 in EA
Last wipe27d agomonthly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 45 on average. Plenty of space to grow.
Standingrank on player hours
59/ 100
C−
Working its way up from the back of the class: #9,134 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 161 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
78/ 100
B
Climbing fast: up 5,205 places this week.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 41% of all ranked servers, top 78% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WW·····
·W·F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h.
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
7d 8hThu 5 Nov, 19:00 UTCFW
35d 8hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 1 OctThu 1 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 21:03 UTCFW27d 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 UTC37d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In Asia, according to its own listing, sits Chagamaru test, with the EA tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 82.21.2.3:10278.
Is Chagamaru test up, and how steady is its uptime?
Right now, Chagamaru test is online. About 4 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
How well does Chagamaru test run?
The average over the last 48 hours was 161 server fps, and it never went below 63. At its peak, it held 118,347 entities, including buildings, deployables and all else in the world. At its highest, it used 4,387 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does Chagamaru test sit?
Rust network protocol 2635 and build 168909 on Linux is what Chagamaru test runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Chagamaru test wipe its map?
The force wipe each month is the only wipe Chagamaru test takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 27 days 13 hours. Its tags record that it wipes monthly.
What happens on Chagamaru test when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 2.
Player count
What position does Chagamaru test hold in the rankings?
In Asia, Chagamaru test is #438, and overall it is #9,134 on player hours over the last seven days, in the top 41% of all ranked servers.
What does the population on Chagamaru test look like?
With 45 slots available, Chagamaru test currently has 0 players. The seven-day average is 0 players, with a peak of 1. The highest average in the last 48 hours came at 13:00 UTC, with 0 players.
Tags
What do Chagamaru test's tags stand for?
You'll see Chagamaru test tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp45 (Max players): Its slot count is 45; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): Players do not fight one another here; the world is the danger; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon; EA (East Asia): In the server browser it appears under East Asia in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Chagamaru test?
These Rust Server Score lists count Chagamaru test among them: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters 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.
Map and rules
What settings and rules apply on Chagamaru test?
Nothing in the name of Chagamaru test states a gather rate. With no change from the game default, groups take up to 8 players. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Chagamaru test?
A procedural map of size 4,750 and seed 2147483647, generated by the game, is what Chagamaru test runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Getting in
How do you get onto Chagamaru test?
Enter client.connect 82.21.2.3:10278 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp45,ptrak,$r?,v2635,^z,^y,^m,EA,^p,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp45
Max playersIts slot count is 45.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
EA
East AsiaIn the server browser it appears 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).