Online EA 82.21.2.3:10278 checked 8m ago
Chagamaru test
Connect
srv = rust.server("82.21.2.3:10279")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 41% of all ranked servers, top 79% in EA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:03 UTC FW26d ago | 0 | NaN | running | 0 |
| 1 | Thu 1 Oct, 12:48 UTC27d ago | 1 | NaN | 0.3 days | 1 |
| 2 | Tue 29 Sep, 13:44 UTC29d ago | 2 | NaN | 2 days | 0 |
| 3 | Tue 22 Sep, 08:01 UTC36d ago | 2 | halved by day 2 | 7.2 days | 0 |
| 4 | Mon 21 Sep, 13:34 UTC37d ago | 2 | NaN | 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本 | EA · groups of 8+ · monthly · 35 on average | 32/100 |
| 1 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 21 on average | 18/88 |
| 2 | [熊猫PVE]修仙升级/召唤/据点/10月新档正式服 | EA · groups of 8+ · monthly · 12 on average | 11/100 |
| 3 | [JP]ちょっぴりHard-PvE RiSu Server | EA · groups of 8+ · monthly · 11 on average | 6/100 |
| 4 | 【青岩-PVE服】原倍/萌新/突袭据点 | EA · groups of 8+ · monthly · 11 on average | 5/200 |
| 5 | 新问仙PVE/死亡不掉/萌新天堂/6个月精心打造/简 | EA · groups of 16+ · monthly · 10 on average | 10/100 |
Quick answers
From the figures on this page.
Population data
What position does Chagamaru test take in the server rankings?
On seven-day player hours Chagamaru test is #9,140 overall and #443 in Asia, inside the top 41% of all ranked servers.
How full does Chagamaru test run?
The sample now reads 0 players for Chagamaru test, out of 45 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 13:00 UTC, averaging 0 players.
Server data
How well does Chagamaru test perform?
Server fps over the last 48 hours averages 177; the floor is 95. The entity count peaked at 117,811, covering buildings, deployables and the rest of the world. The memory field tops out at 4,167 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is Chagamaru test on?
Rust network protocol 2635 and build 168909 on Linux is what Chagamaru test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Chagamaru test, and is it online now?
The current sample puts Chagamaru test online. The uptime it reports puts the last restart about 59 minutes ago. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 13 September 2026.
Where does Chagamaru test sit?
With its EA tag, Chagamaru test lists itself in Asia. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 82.21.2.3:10278.
Settings and map
Which rules apply on Chagamaru test, and what settings?
The name Chagamaru test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: no combat between players. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has Chagamaru test loaded?
Size 4,750, seed 2147483647: the procedural map on Chagamaru test, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.
Wipe schedule
On what schedule does Chagamaru test wipe?
A single wipe each month, the force wipe, is all Chagamaru test does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 26 days 23 hours ago. A monthly wipe schedule is published in its tags.
What is wipe day on Chagamaru test like?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 2.
Tags and filters
Which lists on Rust Data hold Chagamaru test, and which filters?
The Rust Data lists that Chagamaru test fits are: Modded Rust servers 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.
Which meanings do the tags on Chagamaru test hold?
The game's server browser reads these tags from Chagamaru test: gmrust (Game mode): Survival play, standard Rust; mp45 (Max players): Slot count: 45; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join Chagamaru test?
Enter client.connect 82.21.2.3:10278 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.