[JP]SakanaServer
Offline EA 175.177.44.115:28015 checked 12d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 70% of all ranked servers, top 93% in EA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Saturday 31 October, 11:55 UTC, in 1d 16h. Its weekly schedule tag · low confidence
- usual gap
- 15 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
Coming wipes
- in 1d 16hSat 31 Oct, 11:55 UTC
- in 6d 23hThu 5 Nov, 19:00 UTCFW
- in 8d 16hSat 7 Nov, 11:55 UTC
- in 15d 16hSat 14 Nov, 11:55 UTC
- in 22d 16hSat 21 Nov, 11:55 UTC
- in 29d 16hSat 28 Nov, 11:55 UTC
- in 34d 23hThu 3 Dec, 19:00 UTCFW
- in 36d 16hSat 5 Dec, 11:55 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
17 OCT 2026Sat 17 Oct, 11:55 UTC12d ago |
1 | – | running | 0 |
11 OCT 2026Sun 11 Oct, 08:41 UTC18d ago |
1 | held half | 6.1 days | 0 |
17 SEP 2026Thu 17 Sep, 12:48 UTC42d 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.
Quick answers
From the figures on this page.
Map and rules
Where can you read the rules and settings that apply on [JP]SakanaServer?
The name of [JP]SakanaServer does not state a gather rate. 8 players per group is the default limit. Filed under combat training, practice for aim and PvP, with loot given out. Plugins or settings change the game; it is listed under Modded in the server browser. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is enabled.
Which map is in use on [JP]SakanaServer?
A procedural map, generated by the game, is what [JP]SakanaServer runs.
Lists and filters
On Rust Server Index, which lists and filters carry [JP]SakanaServer?
The Rust Server Index lists that include [JP]SakanaServer are Modded Rust servers, filed by play style and Aim training servers, filed. These filters on the server list bring it up: 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.
How should you read the tags listed for [JP]SakanaServer?
The server's own tags are listed here, and the game's server browser reads them: [JP]SakanaServer gives gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2634 (Protocol): Joining needs you on game protocol 2634; cs167781 (Build): Build on file: 167781; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): The region code field is left empty; ^w (Weekly): The server wipes weekly; ^d (Combat training): Loot is given to you for aim and PvP practice; ^o (Oxide): Oxide, also known as uMod, provides the plugin framework; ^z (Modded): This one is Modded, since plugins or settings change how it plays; EA (East Asia): The browser files it under East Asia. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe schedule
What happens on wipe day at [JP]SakanaServer?
The average peak across its recent wipes is 1 players. The latest wipe peaked 1 hours in. The crowd held above half the peak until the next wipe in 100% of its recent wipes.
Which wipe timetable does [JP]SakanaServer follow?
The prediction follows its tag, because too few of [JP]SakanaServer's wipes are on record to confirm the schedule. On Saturday 31 October at 11:55 UTC the next wipe is due. The world it runs now was made 12 days 7 hours. Its tags carry a wipe schedule of once a week.
Population
What position does [JP]SakanaServer hold among Rust servers?
Filed under rankings: #15,224 for [JP]SakanaServer on seven-day player hours, #513 in Asia, top 70% overall.
What does the player count on [JP]SakanaServer look like?
Filed under offline: [JP]SakanaServer, last seen 12 days 6 hours ago.
Server details
Which Rust build is [JP]SakanaServer running?
Rust network protocol 2634 and build 167781, on Linux, is what [JP]SakanaServer runs. Steam keeps your game updated, but the protocol must match for you to join.
What is the uptime and current status of [JP]SakanaServer?
As of now [JP]SakanaServer is offline, with its last appearance 12 days 6 hours ago. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. It was first recorded by Rust Server Index on 17 September 2026.
Which region is [JP]SakanaServer in?
Filed under Asia by its own listing, [JP]SakanaServer carries the EA tag. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 175.177.44.115:28015.
Connecting
How can you connect to [JP]SakanaServer?
Enter client.connect 175.177.44.115:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp100,ptrak,$r?,v2634,^w,^d,EA,gmrust,cs167781,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs167781
ptrak
$r?
Wipe schedule
^w
Gameplay
^d
Mods and access
^o
^z
Region
EA
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.