Rust Data

rustdata.spaceservers139.162.84.157:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 139.162.84.157:28015 checked 2d ago

[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours

quad weekly wipes vanillacarbon

Connect

srv = rust.server("139.162.84.157:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/165 # 0% full
7-day average 0 # peak –
rank #15,318 # top 69%
last wipe 6d ago # weekly schedule
next wipe 19h # Fri 30 Oct, 08:02 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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. 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
15k10k15k20k27 Oct28 Oct29 Oct

Top 69% of all ranked servers, and #620 of the quad servers (top 75%). Ranked on player hours over the last seven days.

Wipe schedule

srv.wipe_schedule()

Next wipe Friday 30 October, 08:02 UTC, in 19h. # Weekly: 7 days after its last wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
139.162.84.157:28015
region
–
max players
165
group limit
quad
wipe schedule
weekly
last wipe
23 Oct 2026, 08:02 UTC
hostname
–
first seen
27 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid HoursEA · quad · weekly · 42 on average0/165
1『小宇宙』10.29号/18:00新开/四人服/萌新服EA · quad · weekly · 21 on average151/200
2『次空间』10.29号/新开/四人服/萌新服EA · quad · weekly · 19 on average3/200
3小虎鲸10.25号|14点新档|四人游玩EA · quad · weekly · 11 on average0/200
4[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid HoursEA · quad · weekly · 6 on average12/165
5TheCove.GG|无权|新手村|四人|10.29号16:00清档EA · quad · weekly · 4 on average1/100

Quick answers

From the figures on this page.

Population data

How does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours compare in the rankings?

Over the last seven days [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours sits at #15,318 on player hours, in the top 69% of ranked servers. The quad group places it at #620.

How full does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours run?

Offline now for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, with the last sample 2 days 3 hours ago. Over the last seven days it averaged 0 players.

Server data

Which Rust version is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours on?

Rust network protocol 2635 and build 168909 on Linux is what [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, and is it online now?

Offline now for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, last seen 2 days 3 hours ago. Uptime of 0% across the last 1 full day: 0 hours of 24. Rust Data logged it first on 27 October 2026.

Where does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours sit?

No region tag is published by [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, 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. 139.162.84.157:28015 is its address.

Rules, settings, map

Which settings and rules does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours run?

No gather rate appears in the name: [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours. Up to 4 players may share a group (quad). Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. Carbon plugins run on it. Its own label is vanilla: facepunch's stock game, with rates, kits and rules untouched. VAC is running: Valve's anti-cheat is on.

Wipes and dates

On what schedule does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours wipe?

Expect an estimate: [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's next wipe is projected from weekly: 7 days after its last wipe. The schedule puts the next wipe on Friday 30 October at 08:02 UTC. This world was created 6 days 4 hours ago. The tags list wipes as weekly.

Tags, lists

Which Rust Data filters and lists contain [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

On Rust Data, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours appears in these lists: Rust community servers, unfiltered and Vanilla Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Vanilla ^v and Carbon ^y; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last week.

How should you read the server tags on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

These tags are published by [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp165 (Max players): 165 slots in total; ts4 (Group limit): Team size tops out at 4; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^w (Weekly): Wipes run weekly; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^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.

How to join

How can I connect to [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

Enter client.connect 139.162.84.157:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp165,ptrak,$r?,v2635,^y,^w,^v,gmrust,cs168909,ts4

Game

gmrust
Game mode Rust survival in its standard form.
mp165
Max players 165 slots in total.
ts4
Group limit Team size tops out at 4.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Wipes run weekly.

Difficulty

^v
Vanilla Facepunch's stock game, with rates, kits and rules untouched.

Mods and access

^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 65,323 players 11,766 servers online