Rust Server Analytics 36,329 players11,615 servers
All servers
Drill-through Server detail

[JP]SakanaServer

Offline EA 175.177.44.115:28015 checked 10d ago

Drill-through
FilterServeris [JP]SakanaServer
Attributes
weekly wipes moddedoxide
Last refreshed
Players now 0/ 100
7-day average 0 peak –
Rank #15,224 top 70% · #513 in EA
Last wipe 10d ago weekly schedule
Next wipe 3d 8h Sat 31 Oct, 11:55 UTC
Capacity 0% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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
15k10k15k20k20 Sep24 Sep13 Oct17 Oct20 Oct24 Oct

Top 70% of all ranked servers, top 93% in EA. Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Saturday 31 October, 11:55 UTC, in 3d 8h. 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

InWhen, UTCKind
3d 8hSat 31 Oct, 11:55 UTCits own
8d 15hThu 5 Nov, 19:00 UTCFW force wipe
10d 8hSat 7 Nov, 11:55 UTCits own
17d 8hSat 14 Nov, 11:55 UTCits own
24d 8hSat 21 Nov, 11:55 UTCits own
31d 8hSat 28 Nov, 11:55 UTCits own
36d 15hThu 3 Dec, 19:00 UTCFW force wipe
38d 8hSat 5 Dec, 11:55 UTCits own

The first 48 hours of its last wipes

Sat 17 OctSun 11 OctThu 17 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
・RUST KILL・XXX|KILL $ CASH|FARM|SHOP|TP|HOME|KITS|PVPVEX10X groups of 10+ · weekly · 5 on average 4 / 100
MINICOPTER / HELICOPTER TRAINING groups of 8+ · 5 on average 2 / 100
PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVP NA · groups of 8+ · 5 on average 5 / 10
[EU] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 EU · no group limit · 4 on average 2 / 100
[US] Rustoria.co RTG - Aimtrain | FaceChecks | Arena | 1v1 NA · no group limit · 2 on average 2 / 100
X1000000.RU|HARDPVP|FUN|FPS++|X1000000000000000000000000000000 groups of 15+ · 1e+06x · weekly · 175 on average 31 / 360

Quick answers

from the figures on this page

Wipe data

When does [JP]SakanaServer wipe?

The prediction follows its tag, because too few of [JP]SakanaServer's wipes are on record to confirm the schedule. Saturday 31 October at 11:55 UTC is the date the next wipe falls on. 10 days 15 hours ago the current world was made. A weekly wipe schedule is published in its tags.

On [JP]SakanaServer, what happens on wipe day?

The average busiest count over recent wipes is 1 players. 1 hours after the latest wipe the crowd peaked. Above half that peak until the next wipe held in 100% of recent wipes.

Server

What is the hosting location of [JP]SakanaServer?

Its EA tag puts [JP]SakanaServer in Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 175.177.44.115:28015.

What Rust build does [JP]SakanaServer run?

On Linux, [JP]SakanaServer runs Rust network protocol 2634 and build 167781. The protocol has to match before you can join; Steam updates it automatically.

What uptime does [JP]SakanaServer show, and is it up?

The current status is offline for [JP]SakanaServer, with the last sighting 10 days 14 hours ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. The first sighting of it by Rust Server Analytics was on 17 September 2026.

Tags

Which meanings do the tags on [JP]SakanaServer carry?

Tags from [JP]SakanaServer, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Capacity of 100 slots; ts8 (Group limit): Team cap of 8, the stock game setting; v2634 (Protocol): To join, your game version must match protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^w (Weekly): A weekly wipe cycle; ^d (Combat training): Training for aim and PvP, loot included; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Plugins or settings change the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does [JP]SakanaServer appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include [JP]SakanaServer: Modded Rust servers: live data and Rust aim training servers. It appears on the server list under the following 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.

Population

Where does [JP]SakanaServer sit among Rust servers?

[JP]SakanaServer holds #15,224 on seven-day player hours and #513 in Asia, inside the top 70% of the ranked field.

At what level does [JP]SakanaServer run its population?

No response from [JP]SakanaServer at the latest check, with a last sighting 10 days 14 hours ago.

Settings

What settings and rules does [JP]SakanaServer use?

Gather rate is not mentioned in the name of [JP]SakanaServer. The game's default 8-player group limit is in force. combat training is the game mode, aim and PvP practice, loot handed out. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. Anti-cheat status: VAC on.

The map on [JP]SakanaServer: which one is it?

The game generates a procedural map for [JP]SakanaServer.

How to join

What is the way onto [JP]SakanaServer?

In the Rust console (F1), enter client.connect 175.177.44.115:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^w,^d,EA,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players Capacity of 100 slots.
ts8
Group limit Team cap of 8, the stock game setting.
v2634
Protocol To join, your game version must match protocol 2634.
cs167781
Build Game build: 167781.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code A region code is not set.

Wipe schedule

^w
Weekly A weekly wipe cycle.

Gameplay

^d
Combat training Training for aim and PvP, loot included.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded Plugins or settings change the game, so it sits under Modded.

Region

EA
East Asia The server browser files it 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.