RUST METRICSFlight deck · live data
Data live Servers11,802 Players69,058 Populated3,653 Fresh wipes 3 h129 Scan5 min
‹ All servers162.222.17.4:28045
Online Full Queue Fresh wipe Wipe due No query

Japan Tokyo - Hard PvE|BPdrop|JP

Online EA 162.222.17.4:28045 checked 11m ago

vanillamoddedcarbonpve
COM 1 · connect

Server instruments

last reading Wed 20:00 UTC
0 25 50 75 100 PAX 1 /100

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 30 SERVER FPS

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 273,997 ×1000

Entities

48 h range 271,926–278,237 · memory 9,263 MB
1239 ET SINCE RESTART 10:53

Uptime

10 h 53 min since its last restart, at the last reading
7-day average10peak 31
Rank#928top 4% · #83 in EA
Last wipe26d agono schedule published
Next wipe–no rhythm it keeps
Memory9,263MB48 h peak 28 players
REC 1

Players

AveragePeak
01020304022:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304022:0007:0016:0001:0010:0020:00

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, measured since 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12505007501k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 4% of all ranked servers, top 15% in EA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap0.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak89players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 2 OctThu 1 Oct
0255075100+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 89, 5 hours in, with 13 in the queue.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 08:46 UTC26d ago 89+13 queue – running 0
Fri 2 Oct, 01:04 UTC26d ago 89+13 queue – 0.3 days 0
Thu 1 Oct, 18:49 UTC FW27d ago 89+13 queue – 0.3 days 3

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 schedule

What should you expect from wipe day on Japan Tokyo - Hard PvE|BPdrop|JP?

At their busiest, its recent wipes drew 89 players on average. 5 hours after the wipe the crowd peaked on the latest wipe, with 13 more in the queue.

When does Japan Tokyo - Hard PvE|BPdrop|JP wipe?

No next wipe can be predicted for Japan Tokyo - Hard PvE|BPdrop|JP, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 26 days 12 hours ago.

Tags

Which tags does Japan Tokyo - Hard PvE|BPdrop|JP carry, and what do they mean?

Tags published by Japan Tokyo - Hard PvE|BPdrop|JP, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts16 (Group limit): You may team up with at most 16; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here; EA (East Asia): Its browser listing: East Asia. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Who operates Japan Tokyo - Hard PvE|BPdrop|JP?

The japantokyo.jp hostname on Japan Tokyo - Hard PvE|BPdrop|JP also appears on 3 other servers we track, which points to one operator.

Where does Japan Tokyo - Hard PvE|BPdrop|JP appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Japan Tokyo - Hard PvE|BPdrop|JP: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Vanilla ^v, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Average players: 10+ on average.

Player count

Where does Japan Tokyo - Hard PvE|BPdrop|JP sit in the rankings?

Player hours over the last seven days put Japan Tokyo - Hard PvE|BPdrop|JP at #928, #83 in Asia, in the top 4% of all ranked servers.

What is the population on Japan Tokyo - Hard PvE|BPdrop|JP?

Current headcount on Japan Tokyo - Hard PvE|BPdrop|JP: 1 players, 100 slots available. Seven-day check: 10 players on average. Peak reading: 31. Average at the busiest hour was 25 players, at 12:00 UTC over the last 48 hours.

Server details

What location is Japan Tokyo - Hard PvE|BPdrop|JP hosted in?

Japan Tokyo - Hard PvE|BPdrop|JP gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 162.222.17.4:28045.

What Rust version is Japan Tokyo - Hard PvE|BPdrop|JP on?

Reading: Japan Tokyo - Hard PvE|BPdrop|JP, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

How does Japan Tokyo - Hard PvE|BPdrop|JP perform?

Over the last 48 hours the average was 30 server fps; the floor was 30. Reading: 278,237 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 10,195 MB. Expect lag when fps falls and entities climb.

What is the uptime on Japan Tokyo - Hard PvE|BPdrop|JP, and is it online?

Check: connection. Japan Tokyo - Hard PvE|BPdrop|JP is online at this moment. By its reported uptime, the last restart was roughly 10 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Japan Tokyo - Hard PvE|BPdrop|JP enforce, and what are its settings?

No gather rate appears in the name: Japan Tokyo - Hard PvE|BPdrop|JP. Check: group limit. Up to 16 players. pve, no combat against other players — that is the game mode. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. It describes itself as vanilla. The meaning given: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Japan Tokyo - Hard PvE|BPdrop|JP?

Map: procedural, 5,500, generated by the game, on Japan Tokyo - Hard PvE|BPdrop|JP. Read the map name: Custom Map.

Join

How can you get onto Japan Tokyo - Hard PvE|BPdrop|JP?

Check: join. Open Rust, press F1, then enter client.connect 162.222.17.4:28045. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/AH7FXJ2Xet is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^z,^y,^v,EA,^p,gmrust,cs168909,ts16

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts16
Group limit You may team up with at most 16.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

Region

EA
East Asia Its browser listing: East Asia.

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.