Top Rust ServersObservatory · live
Live Servers11,781 Players84,652 Populated4,188 Fresh wipes · 3h170 Scanevery 5 min

RS-614Modded server

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

Online 162.222.17.4:30040 checked 10m ago

3x weekly wipes moddedcarbon
Connect
Players now
10/ 300
3% full
7-day average
30
peak 125
Rank
#614
top 3%
Last wipe
4d ago
weekly schedule
Next wipe
T− 2d 12h
Fri 16 Oct, 08:31 UTC
Light curve

Players

AveragePeak
02040608020:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Systems telemetry

Server performance

01020304020:0005:0014:0000:0009:0018: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.

Standing

Rank

daily · 1 is best
RankRank in region
120040060080020 Sep25 Sep29 Sep4 Oct8 Oct13 Oct

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

Orbit

Wipe schedule

fixed weekdays

Next wipe Friday 16 October, 08:31 UTC, in 2d 12h. Every Friday at 08:31 UTC · medium 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

  1. T− 2d 12hFri 16 Oct, 08:31 UTC
  2. T− 9d 12hFri 23 Oct, 08:31 UTC
  3. T− 16d 12hFri 30 Oct, 08:31 UTC
  4. T− 22d 23hThu 5 Nov, 19:00 UTCFW
  5. T− 23d 12hFri 6 Nov, 08:31 UTC
  6. T− 30d 12hFri 13 Nov, 08:31 UTC
  7. T− 37d 12hFri 20 Nov, 08:31 UTC
  8. T− 44d 12hFri 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.

Record

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 08:31 UTC4d ago 125 – running 0
Fri 2 Oct, 08:31 UTC11d ago 153+68 queue halved by day 3 7 days 0
Fri 25 Sep, 08:31 UTC18d ago 133+3 queue halved by day 4 7 days 0
Fri 18 Sep, 08:31 UTC25d 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.

Nearby objects

Similar servers

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

Readouts in words

Quick answers

From the figures on this page.

Player activity

How populated is Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP is showing 10 players on 300 slots right now. Its seven-day average is 30 players, with a peak of 125. The busiest point in the last 48 hours was 11:00 UTC, when it averaged 76 players.

What is the ranking of Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

The last seven days of player hours place Japan Tokyo - Limited Raid Hours |3x|PvP|JP at #614, in the top 3% of ranked servers.

Server tags and lists

Where does Japan Tokyo - Limited Raid Hours |3x|PvP|JP show up in Top Rust Servers lists and filters?

These Top Rust Servers lists count Japan Tokyo - Limited Raid Hours |3x|PvP|JP among their servers: Best 3x Rust servers and Top modded Rust servers. These are the filters that bring it up on the server list: 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 week; Gather rate: 3x; Players now: At least 10; Average players: 25+ on average.

What is the meaning of the tags on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

gmrust (Game mode): Standard survival, as in Rust; mp300 (Max players): It has 300 slots; ts8 (Group limit): At most 8 per team, as standard in the game; v2634 (Protocol): Protocol 2634 is required to join; your game must be on the same version; cs167398 (Build): Game build: 167398; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): The region code is left blank; ^w (Weekly): A weekly wipe; ^z (Modded): It appears in Modded, as plugins or settings modify the game; ^y (Carbon): This server uses Carbon for plugins are the tags Japan Tokyo - Limited Raid Hours |3x|PvP|JP publishes, and the game's server browser reads them. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.

Rules, settings, and map

What map is used on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

The map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP is procedural, size 3,800, seed 1337, and generated by the game. You can look at the map on RustMaps from this page, because size and seed determine the map. You will see the map name as Custom Map.

What does Japan Tokyo - Limited Raid Hours |3x|PvP|JP run for rules and settings?

Gather rates on Japan Tokyo - Limited Raid Hours |3x|PvP|JP are 3x, according to its own title. Up to 8 players per group, as the game defaults. survival is the game mode, standard survival: gathering, building and raiding. You can fight and raid other players. The server browser lists it under Modded: plugins or settings alter the game. Carbon plugins are loaded. VAC, Valve's anti-cheat, is enabled.

Server info

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

Rust network protocol 2634 and build 167398 is what Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs, on Linux. Your game needs the same protocol to connect; Steam takes care of updating it.

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

Over the last two days, it ran at an average of 30 server fps, minimum 8. At its peak, it held 180,692 entities: everything from buildings to deployables and more. Memory usage peaked at 5,241 MB. What players experience as lag comes from low fps and a rising entity count.

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

Its name points to Asia, but Japan Tokyo - Limited Raid Hours |3x|PvP|JP publishes no region tag. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. You reach it at 162.222.17.4:30040.

How reliable is Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Right now, Japan Tokyo - Limited Raid Hours |3x|PvP|JP is up and running. The uptime it gives suggests a restart around 21 hours ago. It spent 168 of the last 168 hours online across 7 days, giving 100% uptime. The first time Top Rust Servers saw it was on 13 September 2026.

Wipe cycle

What happens on wipe day on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

The average busiest count over recent wipes is 137 players. The peak of the latest wipe came 4 hours after it began. Half the peak was held until the next wipe in 0% of recent wipes. If the crowd did not stay above half, it fell below that mark by day 4.

On what schedule does Japan Tokyo - Limited Raid Hours |3x|PvP|JP wipe?

The wipe frequency for Japan Tokyo - Limited Raid Hours |3x|PvP|JP is every Friday at 08:31 UTC. The upcoming wipe is set for Friday 16 October at 08:31 UTC. The present world has been live since 4 days 11 hours ago. The tags show a wipe schedule of one week.

Connection

How can I connect to Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

To connect manually, open the console with F1 and type client.connect 162.222.17.4:30040. Or click Launch Rust on this page to open Rust through Steam and connect directly. For its site, go to https://discord.com/invite/AH7FXJ2Xet.

Spectrum

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival, as in Rust.
mp300
Max players It has 300 slots.
ts8
Group limit At most 8 per team, as standard in the game.
v2634
Protocol Protocol 2634 is required to join; your game must be on the same version.
cs167398
Build Game build: 167398.
ptrak
Networking The network layer is RakNet, which is standard for Rust.
$r?
Region code The region code is left blank.

Wipe schedule

^w
Weekly A weekly wipe.

Mods and access

^z
Modded It appears in Modded, as plugins or settings modify the game.
^y
Carbon This server uses 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.