StatusLive Servers online11,747 Players58,097 Populated3,441 Wiped · 3 h134 Interval5 min Date27 OCT 2026

DWG RG-S0916Server sheetchecked 13m ago

Japan Tokyo - Hard PvE|BPdrop|JP

Online EA 162.222.17.4:28045 checked 13m ago

vanillamoddedcarbonpve
Connect
Players now 2/ 100 2% full
7-day average11peak 33
Rank#916top 4% · #78 in EA
Last wipe25d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
01020304000:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

Fig. 1Players on Japan Tokyo - Hard PvE|BPdrop|JP
Fig. 2

Server performance

01020304000:0009:0018:0004:0013: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12505007501k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 08:46 UTC25d ago 89+13 queue – running 0
Fri 2 Oct, 01:04 UTC25d ago 89+13 queue – 0.3 days 0
Thu 1 Oct, 18:49 UTC FW26d ago 89+13 queue – 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average
20 / 200
02
QS『鱼山路』pve|耐玩|升级|突袭EA · groups of 8+ · 36 on average
17 / 100
03
[坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 36 on average
9 / 100
04
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 21 on average
17 / 88
05
[JP][PVE] パグさば Pug-Server ver 27 | 10/2~EA · groups of 16+ · 14 on average
2 / 100
06
[纪元PVE] 工业|挂机|自动|死亡不掉|标点EA · groups of 8+ · 13 on average
3 / 100
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

What uptime is recorded for Japan Tokyo - Hard PvE|BPdrop|JP, and is it up?

Japan Tokyo - Hard PvE|BPdrop|JP is up at this moment. Counted from its reported uptime, the last restart was about 1 hours ago. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 13 September 2026.

How does Japan Tokyo - Hard PvE|BPdrop|JP perform, as measured?

Average server fps over the last 48 hours is 30; the lowest was 30. Counted at its highest: 279,665 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 10,195 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for Japan Tokyo - Hard PvE|BPdrop|JP?

In Asia Japan Tokyo - Hard PvE|BPdrop|JP lists itself, tagged EA. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 162.222.17.4:28045.

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

On Linux, Japan Tokyo - Hard PvE|BPdrop|JP runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Population

What player count is recorded on Japan Tokyo - Hard PvE|BPdrop|JP?

Current player count on Japan Tokyo - Hard PvE|BPdrop|JP: 2, of 100 slots. Averaged across seven days, the player count is 11, with a peak of 33. The 48-hour peak falls at 12:00 UTC, averaging 24 players.

Against other Rust servers, where is Japan Tokyo - Hard PvE|BPdrop|JP placed?

The same seven-day player-hour count places Japan Tokyo - Hard PvE|BPdrop|JP at #78 within Asia, #916 across all ranked servers and in the top 4% of them.

Schedules

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

An average of 89 players was recorded at the busiest point of its recent wipes. With 13 more waiting in the queue, the crowd on the latest wipe peaked 5 hours after the wipe.

What wipe schedule has been recorded for Japan Tokyo - Hard PvE|BPdrop|JP?

No next wipe can be predicted for Japan Tokyo - Hard PvE|BPdrop|JP: its wipes fall at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 25 days 14 hours ago.

Rules and settings

Which rules and settings are recorded for Japan Tokyo - Hard PvE|BPdrop|JP?

No gather rate is stated in the name of Japan Tokyo - Hard PvE|BPdrop|JP. 16 players is the published group limit. pve, no fighting other players, is the game mode. Plugins or settings change the game, and the browser lists it as Modded. Carbon plugins are run on it. It describes itself as vanilla, by which it means rates, kits and rules are unchanged from Facepunch's release. Anti-cheat: VAC, from Valve, is on.

Which map has Japan Tokyo - Hard PvE|BPdrop|JP loaded?

Generated by the game and procedural, the map measures 5,500 on Japan Tokyo - Hard PvE|BPdrop|JP. The map is named as follows: Custom Map.

Lists and filters

Where does Japan Tokyo - Hard PvE|BPdrop|JP appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry Japan Tokyo - Hard PvE|BPdrop|JP are: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: 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.

Which meaning is attached to each tag on Japan Tokyo - Hard PvE|BPdrop|JP?

Tags published by Japan Tokyo - Hard PvE|BPdrop|JP, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): Slots: 100; ts16 (Group limit): The team limit is 16; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^p (PvE): The world is the danger; players do not fight each other; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon; EA (East Asia): The browser's listing places it under East Asia. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

By whom is Japan Tokyo - Hard PvE|BPdrop|JP run?

A japantokyo.jp hostname is published by Japan Tokyo - Hard PvE|BPdrop|JP, as it is by 3 other servers we track; the same operator most likely runs them.

How to join

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

In Rust, press F1 and type client.connect 162.222.17.4:28045 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://discord.com/invite/AH7FXJ2Xet is its website.

NotesAnswered from the figures
Key

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 standard Rust style.
mp100
Max players Slots: 100.
ts16
Group limit The team limit is 16.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Gameplay

^p
PvE The world is the danger; players do not fight each other.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon The plugin framework is Carbon.

Region

EA
East Asia The browser's listing places it 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.

KeyTag string decoded