[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours
58.191.44.180:28015 checked 12m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 3% of all ranked servers, and #34 of the quad servers (top 4%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 16 October, 07:19 UTC, in 1d 13h. Every Friday at 07:19 UTC · high confidence
- usual gap
- 7 days between real wipes
- on rhythm
- 100% of its recent wipes
- wipe-day peak
- 135 players, last three wipes
- crowd held
- 0% else halves by day 3
Coming wipes
- 1d 13hFri 16 Oct, 07:19 UTC
- 8d 13hFri 23 Oct, 07:19 UTC
- 15d 13hFri 30 Oct, 07:19 UTC
- 22d 1hThu 5 Nov, 19:00 UTCFW
- 22d 13hFri 6 Nov, 07:19 UTC
- 29d 13hFri 13 Nov, 07:19 UTC
- 36d 13hFri 20 Nov, 07:19 UTC
- 43d 13hFri 27 Nov, 07:19 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 139, 6 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 07:19 UTC 5d ago | 139 | – | running | 2 |
| Fri 2 Oct, 07:32 UTC 12d ago | 133 | halved by day 3 | 7 days | 8 |
| Thu 1 Oct, 19:02 UTCFW 12d ago | 133 | – | 0.5 days | 0 |
| Fri 25 Sep, 08:41 UTC 19d ago | 151 | halved by day 2 | 6.4 days | 2 |
| Fri 18 Sep, 06:59 UTC 26d ago | 149 | halved by day 4 | 7.1 days | 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.
Similar servers
Quick answers
Player Count
What is the rank of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
Over the last seven days, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours ranks #624 in player hours, which is in the top 3% of ranked servers. In the quad category, its position is #34.
Is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours busy?
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours: 4 players now, with 165 slots available. The seven-day average player count stands at 29, and the highest point was 139. In the last 48 hours, 13:00 UTC saw the highest activity, with an average of 37 players.
Tags and Filters
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours tags: what do they indicate?
The game's server browser reads these tags from [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours: gmrust (Game mode): Survival as standard in Rust; mp165 (Max players): The server has 165 slots; ts4 (Group limit): Team size is capped at 4; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs167781 (Build): Game build number: 167781; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): Region code missing; ^w (Weekly): Wipe cycle: weekly; ^v (Vanilla): As Facepunch ships the game: rates, kits and rules unchanged; ^y (Carbon): Plugin framework: Carbon. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours operator: who is it?
The nekonection.com hostname published by [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours is used by no other server we track.
Which lists and filters on BestRustServers.xyz contain [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
The BestRustServers.xyz lists that include [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours are: Rust community servers, ranked and Vanilla-tagged Rust servers. It appears under these filters 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; Average players: 25+ on average.
Server Information
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours Rust version: which one?
The combination is Rust network protocol 2634 and build 167781 on Linux for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours smooth?
Over 48 hours, it averaged 56 server fps; the lowest was 42. The entity count reached 111,371, covering buildings, deployables and all other world objects. The maximum memory used was 4,366 MB. A climbing entity count and low fps are felt by players as lag.
What is the uptime and reliability of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
At the moment, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours is up. About 21 hours ago is when it last restarted, based on its uptime. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by BestRustServers.xyz on 13 September 2026.
Where can [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours be found?
Without a region tag, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's name points to Asia. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. You can reach it at 58.191.44.180:28015.
Settings & Map
Which map is used on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
On [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, the map is procedural, size 3,500 with seed 1337, generated by the game. On RustMaps, from this page, the same size and seed show the same map. Map: Custom Map.
[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours rules and settings: what are they?
The name [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours carries no gather multiplier. Listed group: quad, capped at 4 players. Listed as survival, gather, build, raid: the standard game. Fighting and raiding between players are allowed. Under Community in the server browser, it is a community server. Plugin count: Carbon. Vanilla is the label it uses: as Facepunch ships the game: rates, kits and rules unchanged. VAC protection is on.
Wipe Information
On what schedule does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours wipe?
The wipe rhythm of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours is every Friday at 07:19 UTC. Friday 16 October at 07:19 UTC is when the next wipe is due. Its world dates from 5 days 10 hours. The tags state a weekly wipe cycle.
On [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, what occurs on wipe day?
The average busiest point of its recent wipes was 135 players. 6 hours into the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. When it fell, the crowd dropped under half by day 3.
How to Join
How can I connect to [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
Use the F1 console: client.connect 58.191.44.180:28015. Launch Rust on this page does the same by opening Rust through Steam and connecting. https://jhs.nekonection.com is its website.
Server tags
Published as mp165,ptrak,$r?,v2634,^y,^w,^v,gmrust,cs167781,ts4
Game
gmrust- Game mode Survival as standard in Rust.
mp165- Max players The server has 165 slots.
ts4- Group limit Team size is capped at 4.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs167781- Build Game build number: 167781.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code Region code missing.
Wipe schedule
^w- Weekly Wipe cycle: weekly.
Difficulty
^v- Vanilla As Facepunch ships the game: rates, kits and rules unchanged.
Mods and access
^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.