Working its way up from the back of the class: #14,397 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
52/ 100
D
Moving up: up 707 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No hourly history yet.
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 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.
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
RankRank in region
Top 63% of all ranked servers. 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 Thursday 5 November, 19:00 UTC, in 8d 9h.
The force 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
SAKISAKI X100 RUSTSAKI leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 105.154.89.92:28015.
How dependable is SAKISAKI X100 RUSTSAKI, and is it online at the moment?
At this moment, SAKISAKI X100 RUSTSAKI is offline; the last time it was seen was 24 days 13 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 3 October 2026.
Which Rust version is SAKISAKI X100 RUSTSAKI running?
The server SAKISAKI X100 RUSTSAKI is on Rust network protocol 2634 and build 166652 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does SAKISAKI X100 RUSTSAKI reset?
The next wipe on SAKISAKI X100 RUSTSAKI is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 24 days 15 hours. The tags show a monthly wipe schedule.
Population
Where does SAKISAKI X100 RUSTSAKI sit among Rust servers?
In the top 63% of all ranked servers, SAKISAKI X100 RUSTSAKI sits at #14,397 for player hours over the last seven days.
Is SAKISAKI X100 RUSTSAKI a busy server?
The last sighting of SAKISAKI X100 RUSTSAKI was 24 days 13 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on SAKISAKI X100 RUSTSAKI?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags SAKISAKI X100 RUSTSAKI publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show SAKISAKI X100 RUSTSAKI?
Rust Server Score lists that include SAKISAKI X100 RUSTSAKI: Rust servers above 10x gather rate and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: More than 10x.
Map and rules
Which rules does SAKISAKI X100 RUSTSAKI enforce, and what are its settings?
Going by its name, SAKISAKI X100 RUSTSAKI runs 100x gather. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Connecting
What is the way to join SAKISAKI X100 RUSTSAKI?
Enter client.connect 105.154.89.92:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 momentum (D); standing is the one to work on (F).