Rust Data

rustdata.spaceservers162.222.17.4:28046.ipynb

Run all rust-data · live

‹ All servers

Online EA 162.222.17.4:28045 checked 12m ago

Japan Tokyo - Hard PvE|BPdrop|JP

vanillamoddedcarbonpve

Connect

srv = rust.server("162.222.17.4:28046")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 10 # peak 31
rank #926 # top 4% · #83 in EA
last wipe 26d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
01020304000:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304000:0009:0018:0003:0012:0022: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 08:46 UTC26d ago 89+13 queue NaN running 0
1 Fri 2 Oct, 01:04 UTC26d ago 89+13 queue NaN 0.3 days 0
2 Thu 1 Oct, 18:49 UTC FW27d ago 89+13 queue NaN 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.

display(srv.map, srv.info())

Map

5500 · seed 0
Custom map, no picture published
map
Custom Map
size
5500
seed
–

Server

srv.info()
address
162.222.17.4:28045
region
EA
max players
100
group limit
16 max
wipe schedule
–
last wipe
2 Oct 2026, 08:46 UTC
hostname
pvemod.japantokyo.jp
first seen
13 Sep 2026

Operator · japantokyo.jp

rust.servers(operator="japantokyo.jp").sort_values("players")

4 servers publish a japantokyo.jp hostname.

About this server · in its own words

print(srv.description)
次のワイプ予定日:11/6 18:00(サーバー停止は当日午前3時) オリジナルMOD多数!ある程度Rustに慣れている方向けのハードPvEです BPドロップ制なのでリサーチテーブルやテックツリーは使えません。 鋭意開発中でベータ版ですが、現在ボスが充実しています(15体以上) ステータス、スキルツリー、エンチャント、クエスト、フリーマーケットなどMMORPGチックなシステムに加え、次シーズンへのアイテム引き継ぎ機能もあり、やり応え抜群! 毎期多くのアップデートを実施中! ※ベータ版のため不具合が多く発生する可能性があります。ご了承ください。

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average14/200
1QS『鱼山路』pve|耐玩|升级|突袭EA · groups of 8+ · 37 on average41/100
2[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼EA · groups of 8+ · monthly · 35 on average16/100
3爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 21 on average14/88
4[JP][PVE] パグさば Pug-Server ver 27 | 10/2~EA · groups of 16+ · 14 on average6/100
5[纪元PVE] 工业|挂机|自动|死亡不掉|标点EA · groups of 8+ · 13 on average3/100

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Japan Tokyo - Hard PvE|BPdrop|JP rank?

Ranked #926 on seven-day player hours, Japan Tokyo - Hard PvE|BPdrop|JP is #83 in Asia and in the top 4% of all ranked servers.

How full does Japan Tokyo - Hard PvE|BPdrop|JP run?

Japan Tokyo - Hard PvE|BPdrop|JP reports 1 players at this refresh, with 100 slots configured. Over the last seven days it averaged 10 players and peaked at 31. Peak hour in the last 48 hours: 12:00 UTC, mean 25 players.

About the server

How smoothly does Japan Tokyo - Hard PvE|BPdrop|JP run?

The 48-hour average is 30 server fps, with a low of 30. Buildings, deployables and all else in the world took the count as high as 278,237 entities. The memory field tops out at 10,195 MB. Low fps plus an entity count on the way up is the lag players report.

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

The build is Rust network protocol 2635 and build 168909 on Linux, run by Japan Tokyo - Hard PvE|BPdrop|JP. Joining needs the same protocol on your game; Steam handles the update.

Is Japan Tokyo - Hard PvE|BPdrop|JP up, and what does its uptime show?

Online is the state at the latest refresh for Japan Tokyo - Hard PvE|BPdrop|JP. A restart about 53 minutes ago is what its reported uptime implies. 168 of 168 hours up over the last 7 full days, or 100%. Rust Data logged it first on 13 September 2026.

Which location does Japan Tokyo - Hard PvE|BPdrop|JP run from?

The EA tag is what Japan Tokyo - Hard PvE|BPdrop|JP uses to list itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 162.222.17.4:28045.

Map and rules

Which rules apply on Japan Tokyo - Hard PvE|BPdrop|JP, and what settings?

No gather rate appears in the name: Japan Tokyo - Hard PvE|BPdrop|JP. 16 players is the maximum per group. pve is the game mode here, and no combat between players. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Its own label is vanilla: facepunch's stock game, with rates, kits and rules untouched. Anti-cheat status: VAC on.

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

Generated by the game at size 5,500, the map on Japan Tokyo - Hard PvE|BPdrop|JP is procedural. Under map name you will find: Custom Map.

Wipe schedule

On what schedule 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 runs, and no Rust server is exempt. The world it runs now was generated 26 days 14 hours ago.

What is wipe day on Japan Tokyo - Hard PvE|BPdrop|JP like?

Recent wipes averaged 89 players at their peak. 5 hours after the latest wipe the crowd peaked, and 13 more were queued.

Tags, lists

Which lists on Rust Data hold Japan Tokyo - Hard PvE|BPdrop|JP, and which filters?

These Rust Data lists include Japan Tokyo - Hard PvE|BPdrop|JP: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: 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.

Who is behind Japan Tokyo - Hard PvE|BPdrop|JP?

A japantokyo.jp hostname is published by Japan Tokyo - Hard PvE|BPdrop|JP and by 3 other servers we track, which suggests the same operator runs them.

Which meanings do the tags on Japan Tokyo - Hard PvE|BPdrop|JP hold?

The game's server browser reads these tags from Japan Tokyo - Hard PvE|BPdrop|JP: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts16 (Group limit): Team size tops out at 16; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon; EA (East Asia): East Asia is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into Japan Tokyo - Hard PvE|BPdrop|JP?

The manual route: launch Rust, F1, then client.connect 162.222.17.4:28045. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/AH7FXJ2Xet is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts16
Group limit Team size tops out at 16.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla Facepunch's stock game, with rates, kits and rules untouched.

Gameplay

^p
PvE No player-versus-player combat; the danger comes from the world.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon Plugin framework: Carbon.

Region

EA
East Asia East Asia is its listing in the server browser.

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.

Rust Data 53,534 players 11,735 servers online