Working its way up from the back of the class: #13,050 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
33/ 100
F
Lost ground: down 4,336 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 59% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WWW····
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap0.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Wed 7 OctTue 6 OctMon 5 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 7 Oct, 12:19 UTC20d ago
2
–
running
0
Tue 6 Oct, 14:34 UTC21d ago
2
–
0.9 days
0
Mon 5 Oct, 15:19 UTC22d ago
2
–
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Sakuya. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 163.44.152.185:28015 is the address to use.
Is Sakuya up, and how steady is its uptime?
The server is down: Sakuya is offline now, with the last sighting 8 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Sakuya running?
The server Sakuya is on Rust network protocol 2634 and build 166652 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Sakuya wipe its map?
Sakuya wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 20 days 20 hours.
What happens on Sakuya when wipe day arrives?
Recent wipes have peaked at 2 players on average. 1 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does Sakuya sit among Rust servers?
In the top 59% of all ranked servers, Sakuya sits at #13,050 for player hours over the last seven days.
Is Sakuya a busy server?
It has been 8 days 5 hours since Sakuya was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Sakuya?
You'll see Sakuya tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Sakuya?
These Rust Server Score lists count Sakuya among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
How is Sakuya set up, and what rules does it keep?
The name of Sakuya gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Sakuya?
A procedural map of size 4,500 and seed 722508191, generated by the game, is what Sakuya runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join Sakuya?
To connect, start Rust, press F1, and type client.connect 163.44.152.185:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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. Even marks across the subjects, from F to F.