Rust Server TrendsSeismic network · station log
Recording Stations11,880 Players98,236 Active3,914 Wipes · 3 h395 48 h

Station EA-964 · recording

Japan Tokyo - Hard PvE|BPdrop|JP

Online EA 162.222.17.4:28045 checked 10m ago

vanillamoddedcarbonpve
Connect
Players now
8/ 100
8% full
Motion · 24 h
M0.8falling
−6 players on the day
7-day average
10
peak 31
Rank
#964
top 4% · #95 in EA
Last wipe
27d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station EA-964 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
8of 100 slots
Motion · 24 h
M0.8falling−6 players
Sharpest hour
+9into Thu 12:00 UTC
Peak · 48 h
28most players in any hour
Channel 1 · calibrated

Players

AveragePeak
01020304017:0002:0011:0021:0006:0015:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

01020304017:0002:0011:0021:0006:0015: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12505007501k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Expected events

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 gap
0.3 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
89players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 08:46 UTC27d ago M1.9rising 89+13 queue – running 0
Fri 2 Oct, 01:04 UTC27d ago M1.9rising 89+13 queue – 0.3 days 0
Thu 1 Oct, 18:49 UTC FW27d ago M1.9rising 89+13 queue – 0.3 days 3

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average
62/ 200
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 37 on average
38/ 100
[坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱 EA · groups of 8+ · monthly · 35 on average
32/ 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average
20/ 88
[纪元PVE] 工业|挂机|自动|死亡不掉|标点 EA · groups of 8+ · 13 on average
16/ 100
[JP][PVE] パグさば Pug-Server ver 27 | 10/2~ EA · groups of 16+ · 13 on average
7/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

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

The procedural map on Japan Tokyo - Hard PvE|BPdrop|JP is size 5,500, generated by the game. The name of its map is Custom Map.

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

No gather rate appears in the name of Japan Tokyo - Hard PvE|BPdrop|JP. Up to 16 players can be in a group. pve is the game mode, no combat against other players. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. By its own description it is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.

Live population

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

A reading taken now shows 8 players on Japan Tokyo - Hard PvE|BPdrop|JP, which has 100 slots. Averaged across the last seven days the population was 10 players, reaching a peak of 31. Averaged over the last 48 hours, the busiest hour was 12:00 UTC at 25 players.

How does Japan Tokyo - Hard PvE|BPdrop|JP rank against other Rust servers?

Japan Tokyo - Hard PvE|BPdrop|JP is #95 in Asia and #964 worldwide on the past week's player hours, within the top 4% of ranked servers.

Operator and location

How reliably does Japan Tokyo - Hard PvE|BPdrop|JP stay online?

Japan Tokyo - Hard PvE|BPdrop|JP is up at the moment. Going by the uptime figure it reports, it restarted about 5 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Does Japan Tokyo - Hard PvE|BPdrop|JP hold a steady tick rate?

The 48-hour average is 30 server fps; 30 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 278,237. Its highest memory use was 10,195 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

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

In Asia Japan Tokyo - Hard PvE|BPdrop|JP lists itself, with the tag EA. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 162.222.17.4:28045.

Which Rust version is Japan Tokyo - Hard PvE|BPdrop|JP running?

Rust network protocol 2635 and build 168909 on Linux is what Japan Tokyo - Hard PvE|BPdrop|JP runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

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

On average, the busiest point of its recent wipes drew 89 players. With 13 more in the queue, the crowd on the latest wipe peaked 5 hours after the wipe.

How often does Japan Tokyo - Hard PvE|BPdrop|JP wipe, and on which days?

There is no next wipe to predict at Japan Tokyo - Hard PvE|BPdrop|JP, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 27 days 7 hours is how long the current world has been running.

Server tags

What do the server tags on Japan Tokyo - Hard PvE|BPdrop|JP mean?

These are the tags Japan Tokyo - Hard PvE|BPdrop|JP publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts16 (Group limit): Each team can hold up to 16; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^p (PvE): You won't fight other players here; the world is what threatens you; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here; EA (East Asia): East Asia is the region it's listed under in the browser. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Japan Tokyo - Hard PvE|BPdrop|JP appear?

You will find Japan Tokyo - Hard PvE|BPdrop|JP on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. You will find it 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.

Which person or group runs Japan Tokyo - Hard PvE|BPdrop|JP?

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

Join the server

How do you connect to Japan Tokyo - Hard PvE|BPdrop|JP?

Enter client.connect 162.222.17.4:28045 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://discord.com/invite/AH7FXJ2Xet.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players 100 slots are available.
ts16
Group limit Each team can hold up to 16.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Difficulty

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

Gameplay

^p
PvE You won't fight other players here; the world is what threatens you.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon Carbon is the plugin framework running here.

Region

EA
East Asia East Asia is the region it's listed under in the 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.