Rust Server Analytics 96,098 players11,882 servers
All servers
Drill-through Server detail

Japan Tokyo - Chill PvE|JP

Online EA 162.222.17.4:30010 checked 11m ago

Drill-through
FilterServeris Japan Tokyo - Chill PvE|JP
Attributes
vanillamoddedcarbonpve
Last refreshed
Players now 6/ 100
7-day average 21 peak 64
Rank #641 top 3% · #30 in EA
Last wipe 25d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 6% full

Players

average and peak, with its wipes marked
AveragePeak
02040608019:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
01020304019:0004:0013:0023:0008:0017: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
RankRank in region
120040060080020 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule

too few wipes seen yet

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
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 08:46 UTC25d ago 127+25 queue – running 1
Thu 1 Oct, 19:46 UTC FW25d ago 127+25 queue – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 60 on average 34 / 200
[坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 EA · groups of 8+ · monthly · 37 on average 27 / 100
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 36 on average 37 / 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 21 on average 19 / 88
[JP][PVE] パグさば Pug-Server ver 27 | 10/2~ EA · groups of 16+ · 14 on average 15 / 100
[纪元PVE] 工业|挂机|自动|死亡不掉|标点 EA · groups of 8+ · 13 on average 13 / 100

Quick answers

from the figures on this page

Wipe data

The wipe schedule for Japan Tokyo - Chill PvE|JP: what is it?

Too few wipes on record for Japan Tokyo - Chill PvE|JP to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 25 days 9 hours ago the current world was made.

On Japan Tokyo - Chill PvE|JP, what happens on wipe day?

Across recent wipes the busiest point averaged 127 players. On the latest wipe 25 more waited in the queue as the crowd peaked 5 hours after the wipe.

Server

Which location hosts Japan Tokyo - Chill PvE|JP?

The EA tag on Japan Tokyo - Chill PvE|JP lists it in Asia. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 162.222.17.4:30010.

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

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

Is Japan Tokyo - Chill PvE|JP up, and how steady is its uptime?

As of the latest refresh, Japan Tokyo - Chill PvE|JP is online. Its reported uptime indicates a restart roughly 8 hours ago. Of 168 hours in the last 7 full days, 168 were up: 100%. The first sighting of it by Rust Server Analytics was on 13 September 2026.

Does Japan Tokyo - Chill PvE|JP perform well?

Over 48 hours the average held at 30 server fps, and the minimum was 24. At its highest the entity count was 573,215, including buildings, deployables and all else. Peak memory was 16,016 MB. Players experience lag as low fps combined with a rising entity count.

Lists and tags

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

The game's server browser reads the tags Japan Tokyo - Chill PvE|JP publishes: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts16 (Group limit): Teams hold no more than 16; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Build number 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^v (Vanilla): Facepunch's game unchanged: no altered rates, kits or rules; ^p (PvE): The threat comes from the world, not other players; ^z (Modded): Modded listing, where plugins or settings change the game; ^y (Carbon): The Carbon plugin framework is installed; EA (East Asia): Its browser listing sits in East Asia. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does Japan Tokyo - Chill PvE|JP appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists Japan Tokyo - Chill PvE|JP fits are: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: 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 operates Japan Tokyo - Chill PvE|JP?

A japantokyo.jp hostname is published by Japan Tokyo - Chill PvE|JP, as by 3 other servers we track, so one operator most likely runs them all.

Player numbers

What position does Japan Tokyo - Chill PvE|JP hold in the server rankings?

Japan Tokyo - Chill PvE|JP holds #641 on seven-day player hours and #30 in Asia, inside the top 3% of the ranked field.

At what level does Japan Tokyo - Chill PvE|JP run its population?

Population at the current refresh: 6 players on Japan Tokyo - Chill PvE|JP, against 100 slots. Averaging 21 players across seven days, the server reached a peak of 64. Across the last 48 hours, 12:00 UTC shows the highest average: 41 players.

Map and rules

What are the settings on Japan Tokyo - Chill PvE|JP, and its rules?

Gather rate is not mentioned in the name of Japan Tokyo - Chill PvE|JP. Players per group: up to 16. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Carbon. Its self-description is vanilla: facepunch's game unchanged: no altered rates, kits or rules. Anti-cheat status: VAC on.

The map on Japan Tokyo - Chill PvE|JP: which one is it?

A procedural map of size 5,500 with seed 1337, generated by the game, runs on Japan Tokyo - Chill PvE|JP. The map is reproducible from its size and seed and can be seen on RustMaps from here. Named map: Custom Map.

How to join

How can a player join Japan Tokyo - Chill PvE|JP?

In the Rust console (F1), enter client.connect 162.222.17.4:30010. Launch Rust on this page also works, opening Rust through Steam and connecting you. Find it online at https://discord.com/invite/AH7FXJ2Xet.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players 100 slots in total.
ts16
Group limit Teams hold no more than 16.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build Build number 168909.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code No region code has been set.

Difficulty

^v
Vanilla Facepunch's game unchanged: no altered rates, kits or rules.

Gameplay

^p
PvE The threat comes from the world, not other players.

Mods and access

^z
Modded Modded listing, where plugins or settings change the game.
^y
Carbon The Carbon plugin framework is installed.

Region

EA
East Asia Its browser listing sits in 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.