Chagamaru test
Online EA 82.21.2.3:10278 checked 13m ago
Server instruments
last reading Wed 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 95 · below 20 is lag, below 10 is badEntities
48 h range 79,701–117,811 · memory 3,285 MBUptime
0 h 59 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 41% of all ranked servers, top 79% in EA. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 22h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 22hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 22hFW
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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 32/100
- 18/88
- 11/100
- 6/100
- 5/200
- 11/100
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on Chagamaru test?
The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2 it fell below half when it didn't.
What wipe timing does Chagamaru test follow?
The only wipe for Chagamaru test is the force wipe, once a month. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 26 days 23 hours ago the current world was made. A monthly wipe schedule is published in its tags.
Tags
How should you read the tags on Chagamaru test?
Tags published by Chagamaru test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp45 (Max players): The server holds 45 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^p (PvE): No fighting between players: the world itself is the hazard; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon; EA (East Asia): Its browser listing: East Asia. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Chagamaru test?
Rust Metrics lists featuring Chagamaru test: Modded Rust servers, checked live and Rust PvE servers. 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 count
What position does Chagamaru test hold among Rust servers?
Player hours over the last seven days put Chagamaru test at #9,161, #443 in Asia, in the top 41% of all ranked servers.
How full does Chagamaru test get?
Current headcount on Chagamaru test: 0 players, 45 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 13:00 UTC, averaging 0 players at that hour.
Server details
What location is Chagamaru test hosted in?
Chagamaru test gives Asia as its location, with the EA tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 82.21.2.3:10278.
What Rust version is Chagamaru test on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Chagamaru test. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on Chagamaru test within range?
Over the last 48 hours the average was 177 server fps; the floor was 95. Reading: 117,811 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,167 MB. Expect lag when fps falls and entities climb.
Is Chagamaru test up, and how often does it stay up?
Check: connection. Chagamaru test is online at this moment. By its reported uptime, the last restart was roughly 59 minutes ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
What settings and rules apply on Chagamaru test?
Reading the name gives no gather rate for Chagamaru test. The group cap is 8 players, which is the default in the game. The mode is pve. Note the following: no combat against other players. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is Chagamaru test on?
Check: map. Procedural, size 4,750, seed 2147483647, generated by the game on Chagamaru test. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.
Connection
How do you connect to Chagamaru test?
To join: start Rust, press F1 and type client.connect 82.21.2.3:10278. Or press Launch Rust here and Steam opens the game and connects you.