RUST METRICSFlight deck · live data
Data live Servers11,884 Players96,135 Populated4,080 Fresh wipes 3 h165 Scan5 min
‹ All servers162.222.17.4:30040
Online Full Queue Fresh wipe Wipe due No query

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

Online 162.222.17.4:30040 checked 11m ago

3x weekly wipes moddedcarbon
COM 1 · connect

Server instruments

last reading Tue 17:00 UTC
0 75 150 225 300 PAX 22 /300

Players now

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

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 182,880 ×1000

Entities

48 h range 166,291–187,722 · memory 5,091 MB
1239 ET SINCE RESTART 20:04

Uptime

20 h 4 min since its last restart, at the last reading
7-day average38peak 171
Rank#417top 2%
Last wipe4d agoweekly schedule
Next wipe2d 13hFri 30 Oct, 08:31 UTC
Memory5,091MB48 h peak 96 players
REC 1

Players

AveragePeak
025507510019:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304019:0004:0013:0023:0008:0017: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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

PLAN

Wipe schedule

fixed weekdays

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

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

Coming wipes

  1. WPT 1Fri 30 Oct, 08:31 UTC2d 13h
  2. WPT 2Thu 5 Nov, 19:00 UTC9d 0hFW
  3. WPT 3Fri 6 Nov, 08:31 UTC9d 13h
  4. WPT 4Fri 13 Nov, 08:31 UTC16d 13h
  5. WPT 5Fri 20 Nov, 08:31 UTC23d 13h
  6. WPT 6Fri 27 Nov, 08:31 UTC30d 13h
  7. WPT 7Thu 3 Dec, 19:00 UTC37d 0hFW
  8. WPT 8Fri 4 Dec, 08:31 UTC37d 13h

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctFri 9 Oct
050100150200+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

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

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 should you expect from wipe day on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

The busiest point of its recent wipes drew 142 players on average. Peak crowd on the latest wipe: 4 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 4 when it didn't.

How often does Japan Tokyo - Limited Raid Hours |3x|PvP|JP wipe, and when?

Wipes on Japan Tokyo - Limited Raid Hours |3x|PvP|JP come every Friday at 08:31 UTC. Due on Friday 30 October at 08:31 UTC is its next wipe. 4 days 10 hours ago the current world was made. A weekly wipe schedule is published in its tags.

Tag meanings

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

Tags published by Japan Tokyo - Limited Raid Hours |3x|PvP|JP, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp300 (Max players): The server holds 300 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^w (Weekly): It wipes each week; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

On Rust Metrics, Japan Tokyo - Limited Raid Hours |3x|PvP|JP sits in these lists: 3x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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.

Occupancy

What position does Japan Tokyo - Limited Raid Hours |3x|PvP|JP hold among Rust servers?

Player hours over seven days put Japan Tokyo - Limited Raid Hours |3x|PvP|JP at #417, in the top 2% of all ranked servers.

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

22 of 300 slots are filled on Japan Tokyo - Limited Raid Hours |3x|PvP|JP right now. Check: players over seven days. Average 38, peak 171. Average at the busiest hour was 92 players, at 14:00 UTC over the last 48 hours.

Server details

Which location does Japan Tokyo - Limited Raid Hours |3x|PvP|JP run from?

Reading: location. Nothing in the tags, but the name of Japan Tokyo - Limited Raid Hours |3x|PvP|JP points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 162.222.17.4:30040.

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

Reading: Japan Tokyo - Limited Raid Hours |3x|PvP|JP, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on Japan Tokyo - Limited Raid Hours |3x|PvP|JP within range?

Check: fps. Average 30 server fps over the last 48 hours, low of 30. Within range. Check: entities. The peak was 187,722, counting buildings, deployables and the rest of the world. Memory peak: 5,366 MB. Expect lag when fps falls and entities climb.

What is the uptime on Japan Tokyo - Limited Raid Hours |3x|PvP|JP, and is it online?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 20 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

How is Japan Tokyo - Limited Raid Hours |3x|PvP|JP configured, and what rules are in force?

Gather rate check: 3x. That comes from the name Japan Tokyo - Limited Raid Hours |3x|PvP|JP. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Size 3,800 and seed 1337: the game generates the procedural map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.

How to join

How can you get onto Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Check: join. Open Rust, press F1, then enter client.connect 162.222.17.4:30040. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://discord.com/invite/AH7FXJ2Xet.

PLACARDS

Server tags

what each one means

Published as mp300,ptrak,$r?,v2635,^z,^y,^w,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp300
Max players The server holds 300 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly It wipes each week.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

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.