Station EA-15224 · no signal
[JP]SakanaServer
Offline EA 175.177.44.115:28015 checked 11d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,224
- top 70% · #513 in EA
- Last wipe
- 11d ago
- weekly schedule
- Next wipe
- 2d 14h
- Sat 31 Oct, 11:55 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
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
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 2d 14h. 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
- 2d 14hSat 31 Oct, 11:55 UTC
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 9d 14hSat 7 Nov, 11:55 UTC
- 16d 14hSat 14 Nov, 11:55 UTC
- 23d 14hSat 21 Nov, 11:55 UTC
- 30d 14hSat 28 Nov, 11:55 UTC
- 35d 21hThu 3 Dec, 19:00 UTCFW
- 37d 14hSat 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 17 Oct, 11:55 UTC11d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 11 Oct, 08:41 UTC17d ago | M0.0▲rising | 1 | held half | 6.1 days | 0 | |
| Thu 17 Sep, 12:48 UTC41d ago | M0.0▲rising | 1 | – | 23.8 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on [JP]SakanaServer?
[JP]SakanaServer uses a procedural map, which the game generates.
Which settings and rules apply on [JP]SakanaServer?
No gather rate appears in the name of [JP]SakanaServer. At the game's default, groups can have up to 8 players. combat training is the game mode, loot is handed out for aim and PvP practice. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on [JP]SakanaServer?
No players are recorded on [JP]SakanaServer at this moment; it is offline, and the last sighting was 11 days 8 hours ago.
How does [JP]SakanaServer rank against other Rust servers?
The last seven days of player hours place [JP]SakanaServer at #15,224, in the top 70% of all ranked servers and #513 in Asia.
Server details
How reliably does [JP]SakanaServer stay online?
No contact with [JP]SakanaServer right now, and the last recorded contact was 11 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 17 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does [JP]SakanaServer run from?
With its EA tag, [JP]SakanaServer lists itself in Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 175.177.44.115:28015 is the address it uses.
Which Rust version is [JP]SakanaServer running?
[JP]SakanaServer is running Rust network protocol 2634 and build 167781 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on [JP]SakanaServer?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 1 hours after the wipe. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
On what timetable does [JP]SakanaServer run its wipes?
The prediction follows its tag, because too few of [JP]SakanaServer's wipes are on record to confirm its schedule. Saturday 31 October at 11:55 UTC is when its next wipe is due. The present world dates from 11 days 9 hours. A weekly wipe schedule is published in its tags.
Lists and tags
What do the server tags on [JP]SakanaServer mean?
Tags published by [JP]SakanaServer and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server has 100 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^w (Weekly): The server wipes every week; ^d (Combat training): Practise aim and PvP with loot provided; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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, and appear at the top of this page.
On which Rust Server Trends lists does [JP]SakanaServer appear?
These Rust Server Trends lists include [JP]SakanaServer: Modded Rust servers, tracked live and Rust aim training servers, live. On the server list, the filters it matches are: 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.
Connecting
How do you connect to [JP]SakanaServer?
To join, enter client.connect 175.177.44.115:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.