[JP]SakanaServer
Offline EA 175.177.44.115:28015 checked 10d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
daily · 1 is bestTop 70% of all ranked servers, top 93% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Saturday 31 October, 11:55 UTC, in 3d 9h. Its weekly schedule tag · low confidence
Coming wipes
- WPT 1Sat 31 Oct, 11:55 UTC3d 9h
- WPT 2Thu 5 Nov, 19:00 UTC8d 16hFW
- WPT 3Sat 7 Nov, 11:55 UTC10d 9h
- WPT 4Sat 14 Nov, 11:55 UTC17d 9h
- WPT 5Sat 21 Nov, 11:55 UTC24d 9h
- WPT 6Sat 28 Nov, 11:55 UTC31d 9h
- WPT 7Thu 3 Dec, 19:00 UTC36d 16hFW
- WPT 8Sat 5 Dec, 11:55 UTC38d 9h
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
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
the same kind of game, then region, group limit, rate and wipes- 1/100
- 0/100
- 4/10
- 2/100
- 0/100
- 17/360
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on [JP]SakanaServer?
The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.
What wipe timing does [JP]SakanaServer follow?
The prediction follows its tag, because too few of [JP]SakanaServer's wipes are on record to confirm its schedule. Due on Saturday 31 October at 11:55 UTC is its next wipe. The world in play was created 10 days 14 hours ago. A weekly wipe schedule is published in its tags.
Tag meanings
How should you read the tags on [JP]SakanaServer?
These are the tags [JP]SakanaServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^w (Weekly): Wipe cycle: weekly; ^d (Combat training): Loot is handed to you on this training server for aim and PvP work; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; EA (East Asia): East Asia is the browser category it sits in. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does [JP]SakanaServer appear in Rust Metrics lists and filters?
On Rust Metrics, [JP]SakanaServer sits in these lists: Modded Rust servers, checked live and Aim training servers, live readings. Reading: server list filters. It comes up under 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.
Occupancy
What position does [JP]SakanaServer hold among Rust servers?
Ranked by seven-day player hours, [JP]SakanaServer sits at #15,224 and #513 in Asia, inside the top 70%.
What is the population on [JP]SakanaServer?
[JP]SakanaServer is not responding; status offline, last seen 10 days 13 hours ago.
Server
Where does [JP]SakanaServer sit?
[JP]SakanaServer gives Asia as its location, with the EA tag. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 175.177.44.115:28015.
What Rust version is [JP]SakanaServer on?
Version check: Rust network protocol 2634 and build 167781 on Linux, run by [JP]SakanaServer. Matching protocol is required to join. Let Steam update your game.
How reliable is [JP]SakanaServer, and is it online now?
Reading: offline. [JP]SakanaServer last answered 10 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Rules and settings
How is [JP]SakanaServer configured, and what rules are in force?
No gather rate appears in the name: [JP]SakanaServer. The group cap is 8 players, which is the default in the game. combat training, practice for aim and PvP, loot provided — that is the game mode. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is [JP]SakanaServer on?
The game generates a procedural map for [JP]SakanaServer.
Connection
What do you do to join [JP]SakanaServer?
Press F1 in Rust and enter client.connect 175.177.44.115:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.