RUST METRICSFlight deck · live data
Data live Servers11,642 Players38,888 Populated2,942 Fresh wipes 3 h70 Scan5 min
‹ All servers124.98.24.0:28015
Offline Full Queue Fresh wipe Wipe due No query

BRUTAL TOKYO TEST1

Offline 124.98.24.0:28015 checked 33d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,666top 71%
Last wipe50d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server 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.

REC 3

Rank

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.

PLAN

Wipe schedule

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

LOG

Wipes

newest first
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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What wipe timing does BRUTAL TOKYO TEST1 follow?

Its rhythm cannot be told from the wipes of BRUTAL TOKYO TEST1 on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 50 days 12 hours ago the current world was made.

Tags

How should you read the tags on BRUTAL TOKYO TEST1?

These are the tags BRUTAL TOKYO TEST1 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon; sc1 (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show BRUTAL TOKYO TEST1?

Rust Metrics lists featuring BRUTAL TOKYO TEST1: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Player count

What position does BRUTAL TOKYO TEST1 hold among Rust servers?

Ranking for BRUTAL TOKYO TEST1: #15,666 on seven-day player hours, top 71% of all ranked servers.

What is the population on BRUTAL TOKYO TEST1?

Status for BRUTAL TOKYO TEST1: offline. Last seen 33 days 15 hours ago.

Server

Which location does BRUTAL TOKYO TEST1 run from?

Reading: location. BRUTAL TOKYO TEST1 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 124.98.24.0:28015.

What Rust version is BRUTAL TOKYO TEST1 on?

Reading: BRUTAL TOKYO TEST1, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is BRUTAL TOKYO TEST1, and is it online now?

BRUTAL TOKYO TEST1 reports offline. The last reading came 33 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does BRUTAL TOKYO TEST1 enforce, and what are its settings?

No gather rate appears in the name: BRUTAL TOKYO TEST1. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on BRUTAL TOKYO TEST1?

Procedural map on BRUTAL TOKYO TEST1, made by the game's generator.

Join

How do you connect to BRUTAL TOKYO TEST1?

Check: join. Open Rust, press F1, then enter client.connect 124.98.24.0:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: Carbon.

Other

sc1
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.