RUST METRICSFlight deck · live data
Data live Servers11,757 Players64,357 Populated3,442 Fresh wipes 3 h196 Scan5 min
‹ All servers31.57.218.227:28015
Offline Full Queue Fresh wipe Wipe due No query

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

Offline 31.57.218.227:28015 checked 10h ago

quad weekly wipes vanillacarbon
COM 1 · connect

Server instruments

last reading Thu 01:00 UTC
0 41 82 124 165 PAX 0 /165

Players now

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

Server fps

48 h low 7 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 110,577 ×1000

Entities

48 h range 110,577–124,438 · memory 2,913 MB
1239 ET SINCE RESTART 06:01

Uptime

6 h 1 min since its last restart, at the last reading
7-day average9peak 51
Rank#1,865top 8%
Last wipe6d agoweekly schedule
Next wipe3d 23hMon 2 Nov, 11:12 UTC
Memory2,913MB48 h peak 51 players
REC 1

Players

AveragePeak
02040608012:0017:0022:0002:0020:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304012:0017:0022:0002:0020:0001: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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

Top 8% of all ranked servers, and #100 of the quad servers (top 12%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Monday 2 November, 11:12 UTC, in 3d 23h. Its weekly schedule tag · low confidence

wipe-day peak51players, last three wipes

Coming wipes

  1. WPT 1Mon 2 Nov, 11:12 UTC3d 23h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 7hFW
  3. WPT 3Mon 9 Nov, 11:12 UTC10d 23h
  4. WPT 4Mon 16 Nov, 11:12 UTC17d 23h
  5. WPT 5Mon 23 Nov, 11:12 UTC24d 23h
  6. WPT 6Mon 30 Nov, 11:12 UTC31d 23h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 7hFW
  8. WPT 8Mon 7 Dec, 11:12 UTC38d 23h

The first 48 hours of its last wipes

020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 51, 26 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 11:12 UTC3d ago 51 – running 0

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 schedule

What happens on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours when wipe day comes?

The busiest point of its recent wipes drew 51 players on average. 26 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours follow?

The prediction follows its tag, because too few of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's wipes are on record to confirm its schedule. On Monday 2 November at 11:12 UTC its next wipe is due. The world in play was created 6 days 3 hours ago. Its tags carry a weekly wipe schedule.

Lists and filters

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

These are the tags [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp165 (Max players): The server holds 165 slots; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^w (Weekly): Wipe cycle: weekly; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which operator is behind [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

The nekonection.com hostname on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours also appears on 2 other servers we track, which points to one operator.

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

Rust Metrics lists featuring [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours: Rust community servers: live readings and Vanilla Rust servers, live. These filters bring it up on the server list: 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.

Player count

What position does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours hold among Rust servers?

Ranking for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours: #1,865 on seven-day player hours, top 8% of all ranked servers. Check: group rank. #100 among quad servers.

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

Reading for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours: offline at this moment; last seen 10 hours ago. Seven-day check: 9 players on average. Peak reading: 51. Check: 48-hour peak. 13:00 UTC, 46 players on average.

Server details

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

Check: location. No region tag comes from [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, but the name points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 31.57.218.227:28015.

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

Rust network protocol 2635 and build 168909 on Linux is the build [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

Over the last 48 hours the average was 20 server fps; the floor was 7. Reading: 124,438 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 3,974 MB. Expect lag when fps falls and entities climb.

Is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours up, and how often does it stay up?

[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours reports offline. The last reading came 10 hours ago. Check: restart. The uptime it reports puts the last restart about 6 hours ago. Reading: 40% uptime over the last 5 full days. It was up 48 of 120 hours. The first sighting on Rust Metrics was 23 October 2026.

Settings and map

What rules does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours enforce, and what are its settings?

Check: gather rate. The name [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours does not state one. The group cap is 4 players, read as quad. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Carbon plugins are running. The server calls itself vanilla, with this meaning: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

What map is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours on?

Size 3,500 and seed 1337: the game generates the procedural map on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours from them. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.

Join

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

Check: join. Open Rust, press F1, then enter client.connect 31.57.218.227:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://jhs.nekonection.com.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp165
Max players The server holds 165 slots.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^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.