Rust Server TrendsSeismic network · station log
Recording Stations11,733 Players61,573 Active3,391 Wipes · 3 h186 48 h

Station XX-512 · recording

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

Online 58.191.44.180:28015 checked 10m ago

quad weekly wipes vanillacarbon
Connect
Players now
0/ 165
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
43
peak 164
Rank
#512
top 2%
Last wipe
6d ago
weekly schedule
Next wipe
20h
Fri 30 Oct, 08:02 UTC
Seismic record · station XX-512 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 165 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Thu 10:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75119:0021:0000:0004:0007:0010:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608019:0021:0000:0004:0007:0010: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
120040060080020 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 2% of all ranked servers, and #28 of the quad servers (top 3%). Ranked on player hours over the last seven days.

Expected events

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 08:02 UTC, in 20h. Every Friday at 08:02 UTC · high confidence

usual gap
7 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
145players, last three wipes
crowd held
0%else halves by day 3

Coming wipes

  1. 20hFri 30 Oct, 08:02 UTC
  2. 7d 7hThu 5 Nov, 19:00 UTCFW
  3. 7d 20hFri 6 Nov, 08:02 UTC
  4. 14d 20hFri 13 Nov, 08:02 UTC
  5. 21d 20hFri 20 Nov, 08:02 UTC
  6. 28d 20hFri 27 Nov, 08:02 UTC
  7. 35d 7hThu 3 Dec, 19:00 UTCFW
  8. 35d 20hFri 4 Dec, 08:02 UTC

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 164, 6 hours in, with 11 in the queue.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 08:02 UTC6d ago M2.2rising 164+11 queue – running 0
Fri 16 Oct, 08:03 UTC13d ago M2.1rising 133 halved by day 3 7 days 0
Fri 9 Oct, 07:19 UTC20d ago M2.1rising 139 halved by day 3 7 days 2
Fri 2 Oct, 07:32 UTC27d ago M2.1rising 133 halved by day 3 7 days 8
Thu 1 Oct, 19:02 UTC FW27d ago M2.1rising 133 – 0.5 days 0
Fri 25 Sep, 08:41 UTC34d ago M2.2rising 151 halved by day 2 6.4 days 2
Fri 18 Sep, 06:59 UTC41d ago M2.2rising 149 halved by day 4 7.1 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
『小宇宙』10.29号/18:00新开/四人服/萌新服 EA · quad · weekly · 21 on average
133/ 200
『次空间』10.29号/新开/四人服/萌新服 EA · quad · weekly · 19 on average
3/ 200
小虎鲸10.25号|14点新档|四人游玩 EA · quad · weekly · 11 on average
0/ 200
1/ 100
nomarust Sat | JP | Vanilla | Weekly EA · quad · weekly · 1 on average
5/ 100
[红牛五倍]10.28日|新档|开荒|激战|爽玩 EA · quad · weekly · 9 on average
9/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

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

[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours runs a procedural map of size 3,500 with seed 1337, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

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

No gather rate appears in the name of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours. The limit for a group is 4 players (quad). survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The plugins run on Carbon. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours right now?

0 of the 165 slots on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours are filled right now. Averaged across the last seven days the population was 43 players, reaching a peak of 164. The busiest point in the last 48 hours came at 10:00 UTC, averaging 0 players.

How does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours rank against other Rust servers?

The last seven days of player hours place [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours at #512, in the top 2% of all ranked servers. The ranking for quad puts it at #28.

Operator and location

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

Right now, you can reach [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours. Going by the uptime figure it reports, it restarted about 15 hours ago. It was up 73% of the time across the last 7 full days: 123 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.

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

The 48-hour average is 30 server fps; 10 is the lowest observed. The world held up to 126,619 entities at its peak, buildings and deployables included. Memory use peaked at 3,845 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours run from?

No region tag comes from [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, though the name points to Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 58.191.44.180:28015 is the address it uses.

What build of Rust does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours use?

[JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

On average, the busiest point of its recent wipes drew 145 players. With 11 more in the queue, the crowd on the latest wipe peaked 6 hours after the wipe. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 3 it fell below half in the wipes where it didn't hold.

On what timetable does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours run its wipes?

every Friday at 08:02 UTC is how [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours wipes. Friday 30 October at 08:02 UTC is when its next wipe is due. The present world dates from 6 days 3 hours. The tags it publishes carry a weekly wipe schedule.

Server tags

What do the server tags on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours mean?

Tags published by [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp165 (Max players): 165 slots are available; ts4 (Group limit): The team limit is 4; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^w (Weekly): Wipes happen weekly; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours appear?

You will find [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours on the following Rust Server Trends lists: Rust community servers without the side modes and Vanilla Rust servers, recorded live. You will find it 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.

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

One operator most likely runs these: [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours and 2 other servers we track, all publishing a nekonection.com hostname.

Connecting

What steps get you onto [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?

Enter client.connect 58.191.44.180:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://jhs.nekonection.com.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp165
Max players 165 slots are available.
ts4
Group limit The team limit is 4.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Wipe schedule

^w
Weekly Wipes happen weekly.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

Mods and access

^y
Carbon Carbon is the plugin framework running 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.