Live coverage · Rust server
Offline BRUTAL TOKYO TEST1 is not on the server list right now. The figures below are from when it was last seen, 33d ago.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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 record holds too few of BRUTAL TOKYO TEST1's wipes to reveal its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. 50 days 19 hours have passed since this world was generated.
These are the Rust Live Stats lists BRUTAL TOKYO TEST1 fits: Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
gmrust (Game mode): Survival here follows standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2633 (Protocol): You need protocol 2633 on your game to get in; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or changed settings alter the game; ^y (Carbon): It uses the plugin framework Carbon; sc1 (Custom tag): You will not find this among Rust's standard tags: the owner or a plugin created it: that is the tag list BRUTAL TOKYO TEST1 publishes for the game's server browser. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
BRUTAL TOKYO TEST1 reads offline at the moment; the last sighting was 33 days 22 hours ago.
On player hours for the past seven days, BRUTAL TOKYO TEST1 sits at #15,666, inside the top 71% of ranked servers.
The name BRUTAL TOKYO TEST1 carries no gather rate. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. Modded is its browser category, where plugins or settings change the game. Carbon plugins are in use. Anti-cheat: VAC from Valve is enabled.
The map on BRUTAL TOKYO TEST1 is procedural, made by the game itself.
There is no region from BRUTAL TOKYO TEST1. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 124.98.24.0:28015.
BRUTAL TOKYO TEST1 operates on Windows with Rust network protocol 2633 and build 164530. Joining requires the same protocol on your game; Steam takes care of updating it.
As of now, BRUTAL TOKYO TEST1 is offline; the last sighting was 33 days 22 hours ago. It was online for 0 of 168 hours in the last 7 full days, or 0% of the time. The first sighting by Rust Live Stats was on 13 September 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 124.98.24.0:28015.