Working its way up from the back of the class: #15,224 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
34/ 100
F
Lost ground: down 4,993 places this week. A strong wipe could turn it round.
A fair term, with more to come.
Strongest in wipe hold (A+); 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.
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.
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 70% of all ranked servers, top 93% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
······W
·····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 Saturday 31 October, 11:55 UTC, in 3d 16h.
Its weekly schedule tag · low confidence
usual gap15 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
3d 16hSat 31 Oct, 11:55 UTC
8d 23hThu 5 Nov, 19:00 UTCFW
10d 16hSat 7 Nov, 11:55 UTC
17d 16hSat 14 Nov, 11:55 UTC
24d 16hSat 21 Nov, 11:55 UTC
31d 16hSat 28 Nov, 11:55 UTC
36d 23hThu 3 Dec, 19:00 UTCFW
38d 16hSat 5 Dec, 11:55 UTC
The first 48 hours of its last wipes
Sat 17 OctSun 11 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 11:55 UTC10d ago
1
–
running
0
Sun 11 Oct, 08:41 UTC16d ago
1
✓ held half
6.1 days
0
Thu 17 Sep, 12:48 UTC40d ago
1
–
23.8 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
The EA tag on [JP]SakanaServer puts it in Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 175.177.44.115:28015.
Is [JP]SakanaServer up, and how steady is its uptime?
At this moment, [JP]SakanaServer is offline; the last time it was seen was 10 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
What Rust version is [JP]SakanaServer on?
Rust network protocol 2634 and build 167781 on Linux is what [JP]SakanaServer runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does [JP]SakanaServer wipe its map?
The prediction follows its tag, because too few of [JP]SakanaServer's wipes are on record to confirm the schedule. It is due to wipe next on Saturday 31 October at 11:55 UTC. 10 days 7 hours have passed since this world was made. Its tags state that it wipes weekly.
What happens on [JP]SakanaServer when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 1 hours after it began. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Population
What position does [JP]SakanaServer hold in the rankings?
In Asia, [JP]SakanaServer is #513, and overall it is #15,224 on player hours over the last seven days, in the top 70% of all ranked servers.
What does the population on [JP]SakanaServer look like?
The last sighting of [JP]SakanaServer was 10 days 6 hours ago, and it is offline right now.
Tags
How should you read the tags on [JP]SakanaServer?
You'll see [JP]SakanaServer tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^d (Combat training): You are given the loot; the point is aim and PvP practice; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EA (East Asia): In the server browser it appears under East Asia 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.
Where does [JP]SakanaServer appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [JP]SakanaServer: Modded Rust servers, graded and Rust combat training servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Weekly ^w, Combat training ^d, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
Rules and settings
How is [JP]SakanaServer set up, and what rules does it keep?
You will find no gather rate in the name of [JP]SakanaServer. The group limit stays at the game's default of 8 players. You get combat training here, loot is handed out for aim and PvP practice. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on [JP]SakanaServer?
A procedural map, generated by the game, is what [JP]SakanaServer runs.
How to join
What is the way to join [JP]SakanaServer?
To connect, start Rust, press F1, and type client.connect 175.177.44.115:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,^d,EA,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Gameplay
^d
Combat trainingYou are given the loot; the point is aim and PvP practice.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EA
East AsiaIn the server browser it appears under East Asia.
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 fair term, with more to come. Strongest in wipe hold (A+); standing is the one to work on (F).