Rust Data

rustdata.spaceservers162.222.17.4:30140.ipynb

Run all rust-data · live

‹ All servers

Online 162.222.17.4:30040 checked 11m ago

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

3x weekly wipes moddedcarbon

Connect

srv = rust.server("162.222.17.4:30140")
print(srv.connect_command)

Right now

srv.summary()
players now 11/300 # 4% full
7-day average 40 # peak 171
rank #439 # top 2%
last wipe 5d ago # weekly schedule
next wipe 23h # Fri 30 Oct, 08:31 UTC

Players

srv.players.plot(range="48h")
AveragePeak
025507510009:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304009:0018:0003:0012:0022:0007: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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
120040060080020 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · fixed weekdays

srv.wipe_schedule()

Next wipe Friday 30 October, 08:31 UTC, in 23h. # 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

inatkind
023hFri 30 Oct, 08:31 UTCwipe
17d 10hThu 5 Nov, 19:00 UTCFW force wipe
27d 23hFri 6 Nov, 08:31 UTCwipe
314d 23hFri 13 Nov, 08:31 UTCwipe
421d 23hFri 20 Nov, 08:31 UTCwipe
528d 23hFri 27 Nov, 08:31 UTCwipe
635d 10hThu 3 Dec, 19:00 UTCFW force wipe
735d 23hFri 4 Dec, 08:31 UTCwipe

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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 08:31 UTC5d ago 171 NaN running 4
1 Fri 16 Oct, 08:31 UTC13d ago 129+39 queue halved by day 5 7 days 3
2 Fri 9 Oct, 08:31 UTC20d ago 125 halved by day 4 7 days 0
3 Fri 2 Oct, 08:31 UTC27d ago 153+68 queue halved by day 3 7 days 0
4 Fri 25 Sep, 08:31 UTC34d ago 133+3 queue halved by day 4 7 days 0
5 Fri 18 Sep, 08:31 UTC41d 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.

display(srv.map, srv.info())

Map

3800 · seed 1337
Map of Japan Tokyo - Limited Raid Hours |3x|PvP|JP
map
Custom Map
size
3800
seed
1337

Server

srv.info()
address
162.222.17.4:30040
region
–
max players
300
group limit
8, the default
wipe schedule
weekly
last wipe
23 Oct 2026, 08:31 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
社会人向けPvPサーバー 【レイド可能時間(JST)】 月〜木: 20:00〜24:00 金: 20:00〜翌2:00 土: 13:00〜翌2:00 日: 13:00〜24:00 【時間外の制限】 敵拠点は破壊不可(船・車両は破壊可) TC保護範囲外の建築物・設置物は時間外でも破壊可 新規TC: 敵TCから100m以上 レイド可能時間中はTC距離制限なし(Rustデフォルト) TC上限: 1人8個 【サーバー設定】 フルワイプ: 金曜18:00〜翌金曜17:00 公式アップデート日は3:00終了 資源3倍 / TC維持費1.2倍 チームUI 8人(8人超・同盟・協力可) /raidtime でレイド状態を確認 再起動: 毎日6:00 【補填】 サーバーダウン等の補填なし 【VIP】 仕様検討中 JumpRust VIP(Japan Tokyo Main / Mondays)は反映されません English: Raid JST: Mon-Thu 20-24 / Fri 20-02 / Sat 13-02 / Sun 13-24 No base raiding off-hours; boats/vehicles excluded Buildings/deployables outside TC protection remain destructible off-hours TC: 100m+ off-hours; unrestricted during raid; max 8/player 3x / TC upkeep 1.2x / Weekly full wipe / Update day ends 03 Team UI 8; larger groups/alliances OK Restart 06 daily / No downtime compensation

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|LongEA · groups of 100+ · 3x · monthly · 7 on average9/120
1ASIA | RPG · Skills · NEW | Casual PvP | 2-5x | Wiped 10/22EA · groups of 8+ · 5x · weekly · 3 on average3/120
2HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORPEA · groups of 8+ · 3x · monthly · 2 on average1/75
3|TW-JP-SEA|Rustyafied 2X Vanilla|MAP WIPE 10/23EA · groups of 12+ · 2x · weekly · 2 on average0/200
4초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3EA · groups of 8+ · 3x · 1 on average0/50
5QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 24 on average32/100

Quick answers

From the figures on this page.

Player counts

What position does Japan Tokyo - Limited Raid Hours |3x|PvP|JP take in the server rankings?

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

How many players does Japan Tokyo - Limited Raid Hours |3x|PvP|JP hold at once?

Current row: 11 players on Japan Tokyo - Limited Raid Hours |3x|PvP|JP, against 300 slots. Over the last seven days it averaged 40 players and peaked at 171. Peak hour in the last 48 hours: 14:00 UTC, mean 78 players.

Server data

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

Averaged over 48 hours: 30 server fps, never under 30. Entity numbers reached 185,989, and that includes buildings, deployables and the rest. The memory field tops out at 6,283 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does Japan Tokyo - Limited Raid Hours |3x|PvP|JP run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by Japan Tokyo - Limited Raid Hours |3x|PvP|JP. The protocol has to match before you can join, and Steam does the updating.

How reliable is Japan Tokyo - Limited Raid Hours |3x|PvP|JP, and is it online now?

The current sample puts Japan Tokyo - Limited Raid Hours |3x|PvP|JP online. Count back 9 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is Japan Tokyo - Limited Raid Hours |3x|PvP|JP hosted?

No region tag is published by Japan Tokyo - Limited Raid Hours |3x|PvP|JP, though its name points to Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 162.222.17.4:30040 is its address.

Settings and map

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

3x gather is what the name states, and the name is Japan Tokyo - Limited Raid Hours |3x|PvP|JP. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.

Which map has Japan Tokyo - Limited Raid Hours |3x|PvP|JP loaded?

Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs a procedural map of size 3,800 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.

Wipe schedule

When does Japan Tokyo - Limited Raid Hours |3x|PvP|JP wipe, and on what schedule?

Wipes on Japan Tokyo - Limited Raid Hours |3x|PvP|JP run every Friday at 08:31 UTC. Friday 30 October at 08:31 UTC is when the next wipe is due. A new world was started 5 days 23 hours ago, and that is the one in play. A weekly wipe schedule is published in its tags.

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

Across recent wipes the busiest point averaged 142 players. The crowd on the latest wipe topped out 4 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 4.

Tags, lists

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

On Rust Data, Japan Tokyo - Limited Raid Hours |3x|PvP|JP appears in these lists: Modded Rust servers and 3x Rust servers, filtered live. Under these filters on the server list, it is listed: 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.

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

The game's server browser reads these tags from Japan Tokyo - Limited Raid Hours |3x|PvP|JP: gmrust (Game mode): Rust survival in its standard form; mp300 (Max players): Slot count: 300; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): Wipes run weekly; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

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

Enter client.connect 162.222.17.4:30040 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/AH7FXJ2Xet.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp300
Max players Slot count: 300.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly Wipes run weekly.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon Runs 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.

Rust Data 44,156 players 11,640 servers online