LiveLive coverage · EA
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 41% of all ranked servers, top 83% in EA. Ranked on player hours over the last seven days.
Coming up · wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 10h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Force wipe
Thursday 1 October 2026, 21:03 UTC FW
Wipe
Thursday 1 October 2026, 12:48 UTC
Wipe
Tuesday 29 September 2026, 13:44 UTC
Wipe
Tuesday 22 September 2026, 08:01 UTC
Wipe
Monday 21 September 2026, 13:34 UTC
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.
The average peak across its recent wipes is 1 players. The crowd on the latest wipe peaked 0 hours in. Half the peak was held until the next wipe in 0% of its recent wipes. In the other cases it dropped under half by day 2.
Once a month is all Chagamaru test wipes, together with the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. The world you are playing on was built 26 days 11 hours. The tags carry a monthly wipe schedule.
The Rust Live Stats lists that include Chagamaru test are Modded Rust servers live now and Rust PvE servers, live now. These filters on the server list bring it up: 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.
gmrust (Game mode): Standard survival, in the Rust style; mp45 (Max players): 45 slots are available; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^m (Monthly): It wipes with Facepunch's force wipe, once each month; ^p (PvE): No player fights another — the danger comes from the world; ^z (Modded): Modded: plugins or changed settings alter the game; ^y (Carbon): The plugins run through Carbon; EA (East Asia): In the server browser it sits under East Asia: that is the tag list Chagamaru test publishes for the game's server browser. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
0 of Chagamaru test's 45 slots are filled right now. Averaged across seven days, 0 players; the peak was 1. Between now and 48 hours back, 13:00 UTC drew the most players, 0 on average.
Seven-day player hours place Chagamaru test at #9,192 overall, in the top 41% of ranked servers and #451 in Asia.
Nothing in the name of Chagamaru test states a gather rate. No custom limit is set, so groups hold the default 8 players. pve applies here, no fighting other players. Modded is its browser category, where plugins or settings change the game. Carbon plugins are in use. VAC is enabled: Valve's anti-cheat.
Size 4,750, seed 2147483647: that is the procedural map the game generates for Chagamaru test. Same size, same seed, same map: RustMaps has it, reachable from this page. Map name, as listed: Custom Map.
By its own EA tag, Chagamaru test sits in Asia. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 82.21.2.3:10278.
The average server fps was 166 over the last 48 hours; the lowest was 29. It supported up to 117,363 entities, covering buildings, deployables and all other objects. Up to 4,108 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.
The setup on Chagamaru test is Rust network protocol 2635 and build 168909 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
Chagamaru test is up and running at this moment. The uptime it reports puts the last restart at about 4 hours ago. 168 of 168 hours were online in the last 7 full days, giving 100% uptime. Rust Live Stats has tracked it since 13 September 2026.
Enter client.connect 82.21.2.3:10278 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.