On the class lists: F (41), with population over 48 hours and no performance mark.
Players now2/ 1651% full
7-day average10peak 28
Rank#3,350top 15%
Last wipe5d agoweekly schedule
Next wipe1d 10hFri 30 Oct, 08:02 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
6/ 100
F
A quiet classroom so far: 10 of 165 on average. Plenty of space to grow.
Standingrank on player hours
85/ 100
A−
Holds a respectable place: #3,350 on player hours.
Uptimehours on the list, last 48
31/ 100
F
Attendance needs work: on the list only 15 of the last 48 hours.
Performanceserver fps, last 48 hours
96/ 100
A+
Runs smoothly: 57 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
No rank history yet.
Top 15% of all ranked servers, and #214 of the quad servers (top 26%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Friday 30 October, 08:02 UTC, in 1d 10h.
Weekly: 7 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
No region tag appears for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, but the name suggests Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. 158.51.109.110:28015 is the address to use.
Is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours up, and how steady is its uptime?
Right now, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours is online. About 1 hours ago, it restarted, based on the uptime it reports. On 28 October 2026, Rust Server Score saw it for the first time.
Does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours perform well?
It averaged 57 server fps over the last 48 hours, with a low of 49. At its peak, it held 113,682 entities, including buildings, deployables and all else in the world. At its highest, it used 3,557 MB of memory. Players feel lag when fps drops and entities pile up.
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 what [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours reset?
The estimate for [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's next wipe comes from weekly: 7 days after its last wipe. Expect the next wipe on Friday 30 October at 08:02 UTC. 5 days 13 hours have passed since this world was made. The tags carry a weekly wipe schedule.
Player count
What position does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours hold in the rankings?
Over the last seven days, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours has #3,350 for player hours, in the top 15% of all ranked servers. It comes #214 among servers in the quad group.
How many players does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours usually have?
Right now, 2 players are on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, which has 165 slots. The seven-day average is 10 players, with a peak of 28. The busiest time in the last 48 hours was 14:00 UTC, with an average of 26 players.
Lists and filters
What do [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's tags stand for?
You'll see [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp165 (Max players): 165 slots are available; ts4 (Group limit): Teams cap out at 4; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^y (Carbon): Carbon provides the plugin framework here in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Who operates [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
The same operator most likely runs [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours and the 2 other servers we track that also publish a nekonection.com hostname.
Where does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours among them: Best community servers, graded and Vanilla Rust servers, graded. 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; Average players: 10+ on average.
Server rules
How is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours set up, and what rules does it keep?
You will find no gather rate in the name of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours. You can have up to 4 players in a group (quad). survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Carbon. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
A procedural map of size 3,500 and seed 1337, generated by the game, is what [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Getting in
How do you get onto [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
To connect, start Rust, press F1, and type client.connect 158.51.109.110:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://jhs.nekonection.com.
Server tags
what each one means
Published asmp165,ptrak,$r?,v2635,^y,^w,^v,gmrust,cs168909,ts4
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp165
Max players165 slots are available.
ts4
Group limitTeams cap out at 4.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^y
CarbonCarbon provides the plugin framework 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.
A term to build on. Strongest in performance (A+); population is the one to work on (F).