Offline 124.98.24.0:28015 checked 34d ago
BRUTAL TOKYO TEST1
Connect
srv = rust.server("124.98.24.0:28017")
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. 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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 124.98.24.0:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Sep 2026, 15:05 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does BRUTAL TOKYO TEST1 rank?
Player hours over seven days put BRUTAL TOKYO TEST1 at #15,666, in the top 71% of the ranked set.
What population does BRUTAL TOKYO TEST1 carry?
Offline now for BRUTAL TOKYO TEST1, with the last sample 34 days 7 hours ago.
Server facts
What Rust version does BRUTAL TOKYO TEST1 run?
The build is Rust network protocol 2633 and build 164530 on Windows, run by BRUTAL TOKYO TEST1. Steam updates your game for you, but the protocol must match to join.
How reliable is BRUTAL TOKYO TEST1, and is it up?
The latest sample has BRUTAL TOKYO TEST1 offline, with a last sighting 34 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 13 September 2026.
Where does BRUTAL TOKYO TEST1 sit?
There is no region published for BRUTAL TOKYO TEST1. Rust Data does not look up where the machine stands; it shows where a server says it is. 124.98.24.0:28015 is its address.
Map and rules
What rules and settings are recorded for BRUTAL TOKYO TEST1?
You will not find a gather rate in the string BRUTAL TOKYO TEST1. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on BRUTAL TOKYO TEST1?
A procedural map runs on BRUTAL TOKYO TEST1, generated by the game.
Wipe data
On what schedule does BRUTAL TOKYO TEST1 wipe?
A rhythm cannot be read from the wipes of BRUTAL TOKYO TEST1 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 51 days 4 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain BRUTAL TOKYO TEST1?
These Rust Data lists include BRUTAL TOKYO TEST1: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on BRUTAL TOKYO TEST1?
Read by the game's server browser, the tags BRUTAL TOKYO TEST1 publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): Build number: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon; sc1 (Custom tag): A plugin or the owner added this; standard Rust does not define it. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join BRUTAL TOKYO TEST1?
Enter client.connect 124.98.24.0:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.