RUST METRICSFlight deck · live data
Data live Servers11,641 Players44,965 Populated3,093 Fresh wipes 3 h105 Scan5 min
‹ All servers162.222.17.4:30010
Online Full Queue Fresh wipe Wipe due No query

Japan Tokyo - Chill PvE|JP

Online EA 162.222.17.4:30010 checked 13m ago

vanillamoddedcarbonpve
COM 1 · connect

Server instruments

last reading Thu 07:00 UTC
0 25 50 75 100 PAX 23 /100

Players now

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

Server fps

48 h low 24 · below 20 is lag, below 10 is bad
0 200 400 600 800 ENT 571,183 ×1000

Entities

48 h range 561,060–576,937 · memory 12,879 MB
1239 ET SINCE RESTART 09:49

Uptime

9 h 49 min since its last restart, at the last reading
7-day average21peak 64
Rank#657top 3% · #33 in EA
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Memory12,879MB48 h peak 37 players
REC 1

Players

AveragePeak
01020304009:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304009:0018:0003:0012:0022:0007: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
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.

PLAN

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.

LOG

Wipes

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

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 happens on Japan Tokyo - Chill PvE|JP when wipe day comes?

The busiest point of its recent wipes drew 127 players on average. 5 hours after the wipe the crowd peaked on the latest wipe, with 25 more in the queue.

When does Japan Tokyo - Chill PvE|JP wipe?

Its rhythm cannot be told from the wipes of Japan Tokyo - Chill PvE|JP 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. The world it runs now was made 26 days 23 hours ago.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts16 (Group limit): Teams are capped at 16; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^p (PvE): No fighting between players: the world itself is the hazard; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon; EA (East Asia): East Asia is the browser category it sits in from Japan Tokyo - Chill PvE|JP. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which operator is behind Japan Tokyo - Chill PvE|JP?

Check: operator. Japan Tokyo - Chill PvE|JP publishes a japantokyo.jp hostname, and 3 other servers we track do too. Same operator, most likely.

Which lists and filters on Rust Metrics show Japan Tokyo - Chill PvE|JP?

These Rust Metrics lists carry Japan Tokyo - Chill PvE|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; Players now: At least 10; Average players: 10+ on average.

Population

What position does Japan Tokyo - Chill PvE|JP hold among Rust servers?

Player hours over the last seven days put Japan Tokyo - Chill PvE|JP at #657, #33 in Asia, in the top 3% of all ranked servers.

What player count does Japan Tokyo - Chill PvE|JP carry?

Current headcount on Japan Tokyo - Chill PvE|JP: 23 players, 100 slots available. Seven-day check: 21 players on average. Peak reading: 64. The last 48 hours peaked at 12:00 UTC, averaging 35 players at that hour.

Operator and location

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

Japan Tokyo - Chill PvE|JP gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 162.222.17.4:30010.

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

Rust network protocol 2635 and build 168909 on Linux is the build Japan Tokyo - Chill PvE|JP runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for Japan Tokyo - Chill PvE|JP?

Check: fps. Average 30 server fps over the last 48 hours, low of 24. Within range. Peak entity count: 576,937. Buildings, deployables and all else included. Check: memory. Peak use was 15,952 MB. Expect lag when fps falls and entities climb.

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

Check: connection. Japan Tokyo - Chill PvE|JP is online at this moment. Reading: uptime. About 9 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is Japan Tokyo - Chill PvE|JP configured, and what rules are in force?

No gather rate appears in the name: Japan Tokyo - Chill PvE|JP. Group size, maximum: 16 players. Mode check gives pve; other players are not fought. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. It describes itself as vanilla. The meaning given: rates, kits and rules are exactly as Facepunch ships them. Check: anti-cheat. VAC, Valve's system, is on.

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

Check: map. Procedural, size 5,500, seed 1337, generated by the game on Japan Tokyo - Chill PvE|JP. The map repeats when size and seed match. Open it on RustMaps from this page. Read the map name: Custom Map.

Join

What do you do to join Japan Tokyo - Chill PvE|JP?

Press F1 in Rust and enter client.connect 162.222.17.4:30010. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://discord.com/invite/AH7FXJ2Xet.

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 Teams are capped at 16.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

Region

EA
East Asia East Asia is the browser category it sits in.

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.