Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO D SRV11,735online PAX53,199playing OCC3,345with players WIPED 3H133
MODModded traffic
Callsign

JPN417↓

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

Online 162.222.17.4:30040 checked 10m ago

3x weekly wipes moddedcarbon
Clearance · join
Players now 5/ 300 2% full
7-day average40peak 171
Rank#417top 2%
Last wipe5d agoweekly schedule
Next wipe1d 8hFri 30 Oct, 08:31 UTC
Track history

Players

AveragePeak
025507510000:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

01020304000:0009:0018:0003:0012: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.

Rank

daily · 1 is best
RankRank in region
120040060080020 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Friday 30 October, 08:31 UTC, in 1d 8h.

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. 1d 8hFri 30 Oct, 08:31 UTC
  2. 7d 19hThu 5 Nov, 19:00 UTCFW
  3. 8d 8hFri 6 Nov, 08:31 UTC
  4. 15d 8hFri 13 Nov, 08:31 UTC
  5. 22d 8hFri 20 Nov, 08:31 UTC
  6. 29d 8hFri 27 Nov, 08:31 UTC
  7. 35d 19hThu 3 Dec, 19:00 UTCFW
  8. 36d 8hFri 4 Dec, 08:31 UTC

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 08:31 UTC5d ago 171 – running 4
Fri 16 Oct, 08:31 UTC12d ago 129+39 queue halved by day 5 7 days 3
Fri 9 Oct, 08:31 UTC19d ago 125 halved by day 4 7 days 0
Fri 2 Oct, 08:31 UTC26d ago 153+68 queue halved by day 3 7 days 0
Fri 25 Sep, 08:31 UTC33d ago 133+3 queue halved by day 4 7 days 0
Fri 18 Sep, 08:31 UTC40d 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 traffic

Similar servers

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

  1. 01MOD
    Callsign JMP889EA · groups of 100+ · 3x · monthly · 7 on average Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long
    Players 3/120
  2. 02MOD
    Callsign RPG017EA · groups of 8+ · 5x · weekly · 3 on average ASIA | RPG · Skills · NEW | Casual PvP | 2-5x | Wiped 10/22
    Players 2/120
  3. 03MOD
    Callsign HQM017EA · groups of 8+ · 3x · monthly · 2 on average HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORP
    Players 1/75
  4. 04MOD
    Callsign SEA016EA · groups of 12+ · 2x · weekly · 2 on average |TW-JP-SEA|Rustyafied 2X Vanilla|MAP WIPE 10/23
    Players 1/200
  5. 05MOD
    Callsign PVE017EA · groups of 8+ · 3x · 1 on average 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3
    Players 1/50
  6. 06MOD
    Callsign QSS026EA · groups of 20+ · weekly · 24 on average QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造
    Players 29/100
ATIS · this server

Quick answers

From the figures on this page.

Filters

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

On Rust Tracker, Japan Tokyo - Limited Raid Hours |3x|PvP|JP sits in these lists: 3x Rust servers: live tracking and Modded servers, tracked live. It comes up under these filters 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; Average players: 25+ on average.

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

These tags are published by Japan Tokyo - Limited Raid Hours |3x|PvP|JP for the game's server browser to read: gmrust (Game mode): Survival as standard Rust plays; mp300 (Max players): Slots: 300; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^w (Weekly): A weekly wipe; ^z (Modded): Under Modded: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Schedule

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

At their busiest, recent wipes averaged 142 players. 4 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 0% of recent wipes. In the other cases, half the peak was lost by day 4.

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

At Japan Tokyo - Limited Raid Hours |3x|PvP|JP the wipes follow a every Friday at 08:31 UTC rhythm. Due on Friday 30 October at 08:31 UTC: its next wipe. Its world went live 5 days 15 hours. Its tags carry a weekly wipe schedule.

Location and Status

Is Japan Tokyo - Limited Raid Hours |3x|PvP|JP up, and how does its uptime hold?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP is up and online at this moment. About 58 minutes ago it restarted last, based on reported uptime. 100% uptime over the last 7 full days, with 168 of 168 hours up. First contact for Rust Tracker: 13 September 2026.

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

Rust network protocol 2635 and build 168909 on Linux is what Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs. Steam updates it for you; your game must share the protocol to join.

How smoothly does Japan Tokyo - Limited Raid Hours |3x|PvP|JP run?

Server fps held an average of 30 across the last 48 hours, never below 30. Maximum entities carried: 185,989, from buildings and deployables to everything else. Peak memory use: 6,283 MB. Lag, as players experience it, comes from low fps and a rising entity count.

Which location is Japan Tokyo - Limited Raid Hours |3x|PvP|JP in?

No region tag from Japan Tokyo - Limited Raid Hours |3x|PvP|JP, but the name points to Asia. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 162.222.17.4:30040.

Player Count

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

Slots 300; players on board 5: that is Japan Tokyo - Limited Raid Hours |3x|PvP|JP now. Peak of 171 in the last seven days, average 40 players. At 14:00 UTC it drew its highest average of the last 48 hours: 78 players.

Where does Japan Tokyo - Limited Raid Hours |3x|PvP|JP sit in the server rankings?

Top 2% of all ranked servers, and #417 on seven-day player hours: Japan Tokyo - Limited Raid Hours |3x|PvP|JP.

Settings

Which settings and rules are confirmed on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

3x gather is what Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs, going by its name. The game's default applies: groups can have up to 8 players. survival is the game mode, gather, build and raid: the standard game. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. The plugin count stands at Carbon. On: VAC, Valve's anti-cheat.

Which map is confirmed for Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Generated by the game from seed 1337, the procedural map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP measures 3,800. Look at it on RustMaps from this page: equal size and seed return the same map. Read the name of its map: Custom Map.

How to Join

What is the way to join Japan Tokyo - Limited Raid Hours |3x|PvP|JP?

Open the console in Rust with F1 after starting the game, then type client.connect 162.222.17.4:30040. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://discord.com/invite/AH7FXJ2Xet.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp300
Max players Slots: 300.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code The region code is unset.

Wipe schedule

^w
Weekly A weekly wipe.

Mods and access

^z
Modded Under Modded: the game is changed by plugins or settings.
^y
Carbon Plugin framework: Carbon.

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.