Skip to the content
Dive report

Japan Tokyo - Limited Raid Hours |3x|PvP|JP

Online 162.222.17.4:30040 checked 10m ago

3x weekly wipes moddedcarbon
Drop in
62/ 300 players now 21% full
347-day averagepeak 129
#549ranktop 2%
1d agolast wipeweekly schedule
5d 13hnext wipeFri 23 Oct, 08:31 UTC

Players

AveragePeakWipe
05010015020019:0004:0013:0023:0008:0017:00Wiped Fri 16 Oct, 08:31 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
01020304019:0004:0013:0023:0008:0017:00Wiped Fri 16 Oct, 08:31 UTCWIPE

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 Sep25 Sep1 Oct6 Oct12 Oct17 Oct

Top 2% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

fixed weekdays

Next wipe Friday 23 October, 08:31 UTC, in 5d 13h. Every Friday at 08:31 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak137players, last three wipes
crowd held0%else halves by day 4

Coming wipes

  • 5d 13h
    Fri 23 Oct, 08:31 UTC
  • 12d 13h
    Fri 30 Oct, 08:31 UTC
  • 19d 0h
    Thu 5 Nov, 19:00 UTC
    FW
  • 19d 13h
    Fri 6 Nov, 08:31 UTC
  • 26d 13h
    Fri 13 Nov, 08:31 UTC
  • 33d 13h
    Fri 20 Nov, 08:31 UTC
  • 40d 13h
    Fri 27 Nov, 08:31 UTC

The first 48 hours of its last wipes

Fri 9 OctFri 2 OctFri 25 Sep
050100150200+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 125, 4 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:31 UTC1d ago – – running 3
Fri 9 Oct, 08:31 UTC8d ago 125 halved by day 4 7 days 0
Fri 2 Oct, 08:31 UTC15d ago 153+68 queue halved by day 3 7 days 0
Fri 25 Sep, 08:31 UTC22d ago 133+3 queue halved by day 4 7 days 0
Fri 18 Sep, 08:31 UTC29d ago 181 halved by day 6 7 days 4

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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and listings

Where does Japan Tokyo - Limited Raid Hours |3x|PvP|JP appear in Rust Going Deep lists and filters?

The Rust Going Deep lists that carry Japan Tokyo - Limited Raid Hours |3x|PvP|JP are: 3x Rust servers, tracked live and Modded Rust servers. You can find it on the server list by these filters: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 3x; Players now: At least 50; Average players: 25+ on average.

How should you read the tags on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

gmrust (Game mode): Survival, as standard Rust does it; mp300 (Max players): The slot count is 300; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167781 (Build): The build number is 167781; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^w (Weekly): It wipes once a week; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): This server relies on Carbon for plugins — that is the tag list Japan Tokyo - Limited Raid Hours |3x|PvP|JP puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.

Server details

Is Japan Tokyo - Limited Raid Hours |3x|PvP|JP lag-free?

It averaged 30 server fps over the last 48 hours, with a low of 26. At its peak it carried 174,286 entities, including buildings and deployables. 5,659 MB was the highest memory it used. What players notice as lag comes from low fps and a rising entity count.

What's the location of Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

There is no region tag on Japan Tokyo - Limited Raid Hours |3x|PvP|JP, but the name hints at Asia. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 162.222.17.4:30040.

What's the uptime like for Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP is up and reachable at the moment. Its reported uptime shows a restart about 20 hours ago. Over the past full 7 days it stayed up for 168 of 168 hours, or 100%. 13 September 2026 is when Rust Going Deep first saw it.

What Rust version is Japan Tokyo - Limited Raid Hours |3x|PvP|JP on?

Rust network protocol 2634 and build 167781 is what Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs, on Linux. The protocol must match to join; Steam will update your game.

Wipe info

When does Japan Tokyo - Limited Raid Hours |3x|PvP|JP wipe?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs on a every Friday at 08:31 UTC wipe cycle. Expect the next wipe on Friday 23 October at 08:31 UTC. This world has been running since 34 hours ago. Its tags carry a wipe schedule that runs weekly.

What can you expect on wipe day at Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

The average peak across recent wipes is 137 players. The peak crowd on the latest wipe came 4 hours in. The crowd held above half that peak until the next wipe in 0% of recent wipes. By day 4, the pop had dropped under half.

Map and rules

What settings are in place on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Gather rates here are 3x, as Japan Tokyo - Limited Raid Hours |3x|PvP|JP announces in its name. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. Carbon plugins are running here. VAC is on: Valve's anti-cheat is active.

What's the map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

A game-generated procedural map of size 3,800 with seed 1337 is in play on Japan Tokyo - Limited Raid Hours |3x|PvP|JP. The map is reproducible from its size and seed, so RustMaps can show it from this page. You will see the map named: Custom Map.

Player count

How many players are on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP is holding 62 players on its 300 slots at the moment. The seven-day average is 34 players, with a peak of 129. At 13:00 UTC in the last 48 hours, the average reached its highest: 120 players.

What's Japan Tokyo - Limited Raid Hours |3x|PvP|JP's rank among Rust servers?

Over the last seven days, Japan Tokyo - Limited Raid Hours |3x|PvP|JP is #549 by player hours, among the top 2% of all ranked servers.

Getting in

What's the process to join Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Open Rust and press F1, then type client.connect 162.222.17.4:30040. Alternatively, click Launch Rust on this page to join via Steam. https://discord.com/invite/AH7FXJ2Xet is its website.

What each one means

Server tags

Published as mp300,ptrak,$r?,v2634,^z,^y,^w,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust does it.
mp300
Max players The slot count is 300.
ts8
Group limit The default team size of 8 applies here.
v2634
Protocol To join, your game has to be on protocol 2634.
cs167781
Build The build number is 167781.
ptrak
Networking RakNet, the network layer Rust uses by default.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly It wipes once a week.

Mods and access

^z
Modded You'll see it in Modded, since plugins or settings modify the game.
^y
Carbon This server relies on Carbon for plugins.

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.