Rust HeatmapInfrared · players
IR live Players89,289 Servers11,829 Warm4,008 Fresh wipes · 3h98 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 0° now Linear · 0–50° · slots

BRUTAL TOKYO TEST1

Offline 124.98.24.0:28015 checked 34d ago

moddedcarbon
Sp1 · players now 0/ 50
0% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
0
7-day average
peak –
#15,666
rank
top 71%
51d ago
last wipe
no schedule published
–
next wipe
no wipe seen yet
UTC checked 34d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server performance

This server has not answered a direct query in the last 48 hours.

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.

Li4Rank

daily · 1 is best
RankRank in region
15k10k15k20k21 Sep23 Sep25 Sep27 Sep29 Sep1 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Bx1Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit
no group limit · 157 on average
205 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10
EU · groups of 8+ · weekly · 128 on average
121 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10
EU · groups of 16+ · weekly · 116 on average
183 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
EU · groups of 16+ · monthly · 90 on average
126 / 700
RustSpain.com | EU Main
EU · groups of 12+ · weekly · 87 on average
19 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
EU · groups of 16+ · monthly · 84 on average
50 / 1000

LogQuick answers

from the figures on this page

Wipe schedule

What is the wipe schedule on BRUTAL TOKYO TEST1?

BRUTAL TOKYO TEST1 has too few wipes on record yet for its rhythm to show. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 51 days 3 hours ago the server made the world it is on now.

Population

How busy is BRUTAL TOKYO TEST1?

Last seen 34 days 6 hours ago, BRUTAL TOKYO TEST1 is offline at the moment.

How does BRUTAL TOKYO TEST1 rank against other Rust servers?

Player hours over seven days put BRUTAL TOKYO TEST1 at #15,666, in the top 71% of ranked servers.

Settings and rules

Which map does BRUTAL TOKYO TEST1 run?

The game generates the procedural map on BRUTAL TOKYO TEST1.

What are the rules and settings on BRUTAL TOKYO TEST1?

No gather rate appears in the name BRUTAL TOKYO TEST1. The group limit is 8 players, which is the game's default. survival is the game mode, standard play: gathering, building and raiding. Combat between players and raiding are both possible. Plugins or settings change the game, and it is listed under Modded in the server browser. Carbon plugins are in use. The server has VAC, Valve's anti-cheat, turned on.

About the server

Which version of Rust does BRUTAL TOKYO TEST1 run?

Rust network protocol 2633 and build 164530 on Windows is what BRUTAL TOKYO TEST1 runs. Your game must run the same protocol to join, and Steam takes care of updating it.

Is BRUTAL TOKYO TEST1 online, and how reliable is it?

BRUTAL TOKYO TEST1 is down just now; the last sighting was 34 days 6 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It first appears in Rust Heatmap records on 13 September 2026.

Where is BRUTAL TOKYO TEST1 located?

A region is not published for BRUTAL TOKYO TEST1. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. To connect, use 124.98.24.0:28015.

Lists and filters

Which Rust Heatmap lists and filters include BRUTAL TOKYO TEST1?

These Rust Heatmap lists include BRUTAL TOKYO TEST1: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

What do the server tags on BRUTAL TOKYO TEST1 mean?

These are the tags BRUTAL TOKYO TEST1 publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp50 (Max players): This server has 50 slots; ts8 (Group limit): The game default applies: 8 per team at most; v2633 (Protocol): Your game must match protocol 2633 to get in; cs164530 (Build): Build 164530; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^z (Modded): Settings or plugins alter the game, which puts it under Modded; ^y (Carbon): Plugins run through Carbon; sc1 (Custom tag): The owner or a plugin set this, which is not a standard Rust tag. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

How to join

How do I join BRUTAL TOKYO TEST1?

Press F1 in Rust to open the console, then enter client.connect 124.98.24.0:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.

KeyServer tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs164530,sc1,ts8,^z,^y

Game

gmrust
Game mode Survival in the standard Rust form.
mp50
Max players This server has 50 slots.
ts8
Group limit The game default applies: 8 per team at most.
v2633
Protocol Your game must match protocol 2633 to get in.
cs164530
Build Build 164530.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code The region code is blank.

Mods and access

^z
Modded Settings or plugins alter the game, which puts it under Modded.
^y
Carbon Plugins run through Carbon.

Other

sc1
Custom tag The owner or a plugin set this, which is not a standard Rust 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.