A quiet classroom so far: 9 of 165 on average. Plenty of space to grow.
Standingrank on player hours
92/ 100
A
Well up the rankings: #1,849 on player hours.
Uptimehours on the list, last 48
35/ 100
F
Attendance needs work: on the list only 17 of the last 48 hours.
Performanceserver fps, last 48 hours
39/ 100
F
Needs to work on its frame rate: 23 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 standing (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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 8% of all ranked servers, and #99 of the quad servers (top 12%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Monday 2 November, 11:12 UTC, in 3d 16h.
Its weekly schedule tag · low confidence
wipe-day peak51players, last three wipes
Coming wipes
3d 16hMon 2 Nov, 11:12 UTC
6d 23hThu 5 Nov, 19:00 UTCFW
10d 16hMon 9 Nov, 11:12 UTC
17d 16hMon 16 Nov, 11:12 UTC
24d 16hMon 23 Nov, 11:12 UTC
31d 16hMon 30 Nov, 11:12 UTC
34d 23hThu 3 Dec, 19:00 UTCFW
38d 16hMon 7 Dec, 11:12 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 51, 26 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
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. Find it at 31.57.218.227:28015.
How reliable is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours, and is it up?
At this moment, [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours is offline; the last time it was seen was 17 hours ago. The uptime it reports puts the last restart at about 6 hours ago. It was up 48 of 120 hours over the last 5 full days, which is 40% of the time. On 23 October 2026, Rust Server Score saw it for the first time.
Is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours smooth to play on?
The average over the last 48 hours was 23 server fps, and it never went below 15. Up to 118,793 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,908 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours on?
You will find [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours wipe its map?
Its tag sets the prediction, as the record holds too few of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours's wipes to confirm its schedule. Expect the next wipe on Monday 2 November at 11:12 UTC. 6 days 10 hours have passed since this world was made. Its tags state that it wipes weekly.
What happens on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours when wipe day arrives?
Recent wipes have peaked at 51 players on average. 26 hours after the latest wipe began, the crowd hit its peak.
Population
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 #1,849 for player hours, in the top 8% of all ranked servers. It comes #99 among servers in the quad group.
Is [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours a busy server?
It has been 17 hours since [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours was last seen, and it is offline right now. The seven-day average is 9 players, with a peak of 51. The busiest time in the last 48 hours was 01:00 UTC, with an average of 4 players.
Tags and filters
How should you read the tags on [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
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): Its slot count is 165; ts4 (Group limit): A team can hold 4 players at most; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^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.
Which person or group runs [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. It shows under the following 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.
Rules and settings
Which rules does [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours enforce, and what are its settings?
Nothing in the name of [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours states a gather rate. You can have up to 4 players in a group (quad). It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. The plugin count runs to Carbon. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours uses?
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. The name of the map reads: Custom Map.
How to join
How should you connect to [JP] Japan Hideaway Server | Solo/Duo/Trio/Quad | Raid Hours?
Enter client.connect 31.57.218.227:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. 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 playersIts slot count is 165.
ts4
Group limitA team can hold 4 players at most.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
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 standing (A); population is the one to work on (F).