Rust Data

rustdata.spaceservers162.222.17.4:30110.ipynb

Run all rust-data · live

‹ All servers

Online EA 162.222.17.4:30010 checked 9m ago

Japan Tokyo - Chill PvE|JP

vanillamoddedcarbonpve

Connect

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

Right now

srv.summary()
players now 34/100 # 34% full
7-day average 21 # peak 64
rank #656 # top 3% · #33 in EA
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
01020304013:0022:0007:0016:0002:0011:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304013:0022:0007:0016:0002:0011: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
120040060080020 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap0.5 daysbetween real wipes
wipe-day peak127players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 08:46 UTC27d ago 127+25 queue NaN running 1
1 Thu 1 Oct, 19:46 UTC FW27d ago 127+25 queue NaN 0.5 days 7

# 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 1337
Map of Japan Tokyo - Chill PvE|JP
map
Custom Map
size
5500
seed
1337

Server

srv.info()
address
162.222.17.4:30010
region
EA
max players
100
group limit
16 max
wipe schedule
–
last wipe
2 Oct 2026, 08:46 UTC
hostname
pvechill.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時) 【基本設定】 Outpostで車両購入が可能 季節限定イベントを定期的に実施 毎日 6:00/18:00 に定期再起動 /otp でOutpostへテレポート可能 【TC関連ルール】 5日以上ログインがない拠点は自動削除対象 (TC登録している誰かがログインすれば維持可能) 【窃盗対策】 ほとんどの物にコードロック装着可 【禁止行為】 他プレイヤーの体験を害する行為は禁止 4人以下のチーム分割禁止(ロック制限回避防止) 5人以上は4人単位で分割可(例: 10人→4+4+2) 違反は運営が個別に判断・措置します 【補填・免責】 アイテム/車両の補填は基本なし(MODバグのみ検討) ヘリ/カーゴ等はサーバー再起動で消滅します データ消失の責任は負いかねます 詳細はDiscordをご確認ください

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 · 58 on average102/200
1QS『鱼山路』pve|耐玩|升级|突袭EA · groups of 8+ · 37 on average46/100
2[坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖EA · groups of 8+ · monthly · 35 on average38/100
3爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average21/88
4[JP][PVE] パグさば Pug-Server ver 27 | 10/2~EA · groups of 16+ · 13 on average12/100
5[纪元PVE] 工业|挂机|自动|死亡不掉|标点EA · groups of 8+ · 13 on average15/100

Quick answers

From the figures on this page.

Player counts

How does Japan Tokyo - Chill PvE|JP compare in the rankings?

Ranked #656 on seven-day player hours, Japan Tokyo - Chill PvE|JP is #33 in Asia and in the top 3% of all ranked servers.

How full does Japan Tokyo - Chill PvE|JP run?

Japan Tokyo - Chill PvE|JP reports 34 players at this refresh, with 100 slots configured. Over the last seven days it averaged 21 players and peaked at 64. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 35 players.

Server data

What does performance look like on Japan Tokyo - Chill PvE|JP?

Averaged over 48 hours: 30 server fps, never under 24. Entity numbers reached 576,937, and that includes buildings, deployables and the rest. The memory field tops out at 15,429 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is Japan Tokyo - Chill PvE|JP on?

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

How reliable is Japan Tokyo - Chill PvE|JP, and is it up?

Online is the state at the latest refresh for Japan Tokyo - Chill PvE|JP. A restart about 1 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does Japan Tokyo - Chill PvE|JP sit?

The EA tag is what Japan Tokyo - Chill PvE|JP uses to list itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 162.222.17.4:30010.

Rules, settings, map

Which settings and rules does Japan Tokyo - Chill PvE|JP run?

The name Japan Tokyo - Chill PvE|JP carries no gather rate. 16 players is the maximum per group. Recorded as pve, no combat between players. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.

Which map has Japan Tokyo - Chill PvE|JP selected?

Japan Tokyo - Chill PvE|JP runs a procedural map of size 5,500 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.

Wipe schedule

When does Japan Tokyo - Chill PvE|JP wipe, and how often?

A rhythm cannot be read from the wipes of Japan Tokyo - Chill PvE|JP on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 3 hours ago.

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

The average peak over recent wipes is 127 players. On the latest wipe the peak came 5 hours after the wipe, with a queue of 25.

Tags, lists

Which Rust Data filters and lists contain Japan Tokyo - Chill PvE|JP?

The Rust Data lists that Japan Tokyo - Chill PvE|JP fits are: Modded Rust servers and Rust PvE servers. It appears under these filters 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; Players now: At least 10; Average players: 10+ on average.

Which operator runs Japan Tokyo - Chill PvE|JP?

Japan Tokyo - Chill PvE|JP and 3 other servers we track both publish a japantokyo.jp hostname, so the same operator most likely runs them.

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

The game's server browser reads these tags from Japan Tokyo - Chill PvE|JP: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts16 (Group limit): The team cap is 16; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins; EA (East Asia): In the server browser it sits under East Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

How can I connect to Japan Tokyo - Chill PvE|JP?

Enter client.connect 162.222.17.4:30010 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. 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 Slot count: 100.
ts16
Group limit The team cap is 16.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Gameplay

^p
PvE Players do not fight each other here; the world supplies the danger.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon Runs on Carbon for plugins.

Region

EA
East Asia In the server browser it sits under 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.

Rust Data 67,745 players 11,776 servers online