Statistical profileOffline
BRUTAL TOKYO TEST1
124.98.24.0:28015 checked 33d ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,666
top 71%
Last wipe
50d ago
no schedule published
Next wipe
–
no wipe seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 50 slots.
- It ranks #15,666 of all ranked servers, the top 71%, on player hours over the last seven days.
- Its current map went up 50d ago.
2. Players
Figure 1: Players on BRUTAL TOKYO TEST1
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 4: Map of BRUTAL TOKYO TEST1
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of BRUTAL TOKYO TEST1
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 161 on average | 32 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 135 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 39 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 15 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 8 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 4 / 1000 |
10. Quick answers
From the figures on this page.
Wipe details
When does BRUTAL TOKYO TEST1 wipe, and how often?
With too few wipes of BRUTAL TOKYO TEST1 on record, its rhythm remains unclear. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The present world dates from 50 days 11 hours.
Server details
Is BRUTAL TOKYO TEST1 up, and how well has it held up?
BRUTAL TOKYO TEST1 is offline at the time of this release; it was last seen 33 days 14 hours ago. Of the 168 hours in the last 7 full days, it was up 0 of them, or 0%. The first sighting of it by Rust Census was on 13 September 2026.
In which location is BRUTAL TOKYO TEST1 based?
No region is published by BRUTAL TOKYO TEST1. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 124.98.24.0:28015 it is addressed.
On which Rust version does BRUTAL TOKYO TEST1 operate?
Rust network protocol 2633 and build 164530 on Windows is the version BRUTAL TOKYO TEST1 runs. Steam updates your game for you, but it has to be on the same protocol to join.
Player counts
What are the current player figures for BRUTAL TOKYO TEST1?
At this release BRUTAL TOKYO TEST1 is offline, having last been seen 33 days 14 hours ago.
What position does BRUTAL TOKYO TEST1 hold in the server rankings?
The rank for BRUTAL TOKYO TEST1 is #15,666 on seven-day player hours, in the top 71% of ranked servers.
Tag details
Which Rust Census filters and lists cover BRUTAL TOKYO TEST1?
Included in these Rust Census lists is BRUTAL TOKYO TEST1: Modded Rust servers, counted. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
What is meant by each tag shown on BRUTAL TOKYO TEST1?
Read by the game's server browser, BRUTAL TOKYO TEST1 publishes these tags: gmrust (Game mode): Survival play, in the standard Rust format; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2633 (Protocol): To connect, your game version must match protocol 2633; cs164530 (Build): Game build: 164530; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game on this modded server; ^y (Carbon): Carbon, a plugin framework, is installed; sc1 (Custom tag): Neither standard nor issued by Facepunch: an owner or plugin applied this tag. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
Which map has been recorded for BRUTAL TOKYO TEST1?
A procedural map runs on BRUTAL TOKYO TEST1, generated by the game.
On BRUTAL TOKYO TEST1, what rules and settings are in force?
No gather rate is recorded for BRUTAL TOKYO TEST1 in its name. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. Modded is its section in the server browser, because plugins or settings change the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Join details
How can you connect to BRUTAL TOKYO TEST1?
Enter client.connect 124.98.24.0:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp50,ptrak,$r?,v2633,gmrust,cs164530,sc1,ts8,^z,^y
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp50 | Max players Slots: 50. |
ts8 | Group limit Teams are capped at 8, the default the game ships with. |
v2633 | Protocol To connect, your game version must match protocol 2633. |
cs164530 | Build Game build: 164530. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code No region code is set. |
Mods and access
^z | Modded Plugins or settings alter the game on this modded server. |
|---|---|
^y | Carbon Carbon, a plugin framework, is installed. |
Other
sc1 | Custom tag Neither standard nor issued by Facepunch: an owner or plugin applied this tag. |
|---|
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.