RUST METRICSFlight deck · live data
Data live Servers11,621 Players32,314 Populated2,788 Fresh wipes 3 h69 Scan5 min
‹ All servers158.51.109.110:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 158.51.109.110:28015 checked 8m ago

quad weekly wipes vanillacarbon
COM 1 · connect

Server instruments

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

Players now

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

Server fps

48 h low 49 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 104,670 ×1000

Entities

48 h range 104,179–113,682 · memory 2,779 MB
1239 ET SINCE RESTART 08:00

Uptime

8 h 0 min since its last restart, at the last reading
7-day average7peak 28
Rank#3,243top 15%
Last wipe5d agoweekly schedule
Next wipe1d 3hFri 30 Oct, 08:02 UTC
Memory2,779MB48 h peak 28 players
REC 1

Players

AveragePeak
01020304005:0009:0013:0019:0023:0003:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608005:0009:0013:0019:0023:0003: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 28 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
11k2k3k4k28 Oct29 Oct

Top 15% of all ranked servers, and #206 of the quad servers (top 25%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Friday 30 October, 08:02 UTC, in 1d 3h. Weekly: 7 days after its last wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
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.

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

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

An estimate from weekly: 7 days after its last wipe gives [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's next wipe. On Friday 30 October at 08:02 UTC its next wipe is due. The world it runs now was made 5 days 20 hours ago. Its tags carry a weekly wipe schedule.

Tags

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

Tags published by [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp165 (Max players): Slots: 165; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^w (Weekly): Check: wipe cycle. Every week; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Who operates [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.

Where does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours appear in Rust Metrics lists and filters?

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

Occupancy

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

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

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

Current headcount on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours: 3 players, 165 slots available. Seven-day check: 7 players on average. Peak reading: 28. Check: 48-hour peak. 14:00 UTC, 26 players on average.

Server

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

Reading: location. Nothing in the tags, but the name of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 158.51.109.110: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. Matching protocol is required to join. Let Steam update your game.

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

Reading: 58 server fps on average across the last 48 hours. It never dropped below 49. Peak entity count: 113,682. Buildings, deployables and all else included. Memory peak: 3,557 MB. What players call lag comes from low fps and an entity count on the rise.

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 online. Status: normal. Reading: uptime. About 8 hours ago it restarted, on its own count. Check: first contact. Rust Metrics logged it on 28 October 2026.

Map and rules

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

Reading the name gives no gather rate for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours. Groups stop at 4 players. The label given is quad. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Check: plugins. It runs Carbon of them. It describes itself as vanilla. The meaning given: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.

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. Check: map view. Size and seed match, so the map is the same; view 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?

Press F1 in Rust and enter client.connect 158.51.109.110:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. 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 Survival, as standard Rust plays it.
mp165
Max players Slots: 165.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Mods and access

^y
Carbon Plugin framework in use: 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.