Rust Server TrendsSeismic network · station log
Recording Stations11,652 Players47,233 Active3,140 Wipes · 3 h114 48 h

Station XX-13568 · no signal

SAKHALIN_ONLINE

Offline 188.113.164.74:28015 checked 1d ago

monthly wipes vanilla
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#13,568
top 61%
Last wipe
7d ago
monthly schedule
Next wipe
7d 10h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-13568 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123409:0010:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608009:0010:00

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, measured since 13 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k13 Oct16 Oct19 Oct23 Oct26 Oct29 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h. The force wipe · high confidence

wipe-day peak
1players, last three wipes

Coming wipes

  1. 7d 10hThu 5 Nov, 19:00 UTCFW
  2. 35d 10hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 21 Oct, 10:36 UTC7d ago M0.0rising 1 – running 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
281/ 325
Rusty Moose |EU Monthly| EU · groups of 12+ · monthly · 216 on average
139/ 200
[EU East] Facepunch 4 EU · groups of 8+ · monthly · 172 on average
63/ 350
[EU] Facepunch 1 EU · groups of 8+ · monthly · 161 on average
81/ 400
Rustopia.gg - US Large NA · groups of 16+ · monthly · 129 on average
42/ 200
Rustafied.com - EU Long - Large EU · groups of 16+ · monthly · 128 on average
49/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on SAKHALIN_ONLINE?

SAKHALIN_ONLINE runs a procedural map of size 4,000 with seed 383838, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on SAKHALIN_ONLINE?

You will find no gather rate in the name of SAKHALIN_ONLINE. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Vanilla is the label it uses for itself: unchanged from Facepunch's release: no altered rates, kits or rules. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on SAKHALIN_ONLINE?

No players are recorded on SAKHALIN_ONLINE at this moment; it is offline, and the last sighting was 46 hours ago. Averaged across the last seven days the population was 0 players, reaching a peak of 1.

How does SAKHALIN_ONLINE rank against other Rust servers?

The last seven days of player hours place SAKHALIN_ONLINE at #13,568, in the top 61% of all ranked servers.

Server details

How reliably does SAKHALIN_ONLINE stay online?

SAKHALIN_ONLINE is down at the moment; the last recorded contact was 46 hours ago. Going by the uptime figure it reports, it restarted about 23 hours ago. 129 of 168 hours in the last 7 full days were up time, 77% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 October 2026.

Does SAKHALIN_ONLINE hold a steady tick rate?

The 48-hour average is 78 server fps; 78 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 94,572. Memory use peaked at 2,476 MB. Low fps together with a growing entity count is what players experience as lag.

Where in the world is SAKHALIN_ONLINE hosted?

No region is published by SAKHALIN_ONLINE. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 188.113.164.74:28015.

Which Rust version is SAKHALIN_ONLINE running?

SAKHALIN_ONLINE is running Rust network protocol 2634 and build 167584 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on SAKHALIN_ONLINE?

On average, the busiest point of its recent wipes drew 1 players. 3 hours into the latest wipe, the crowd reached its peak.

How often does SAKHALIN_ONLINE wipe, and on which days?

At the force wipe each month SAKHALIN_ONLINE wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 7 days 22 hours is how long the current world has been running. Its tags state a monthly wipe schedule.

Tags

What do the server tags on SAKHALIN_ONLINE mean?

The game's server browser reads the tags SAKHALIN_ONLINE publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167584 (Build): Game build: 167584; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules. 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 SAKHALIN_ONLINE appear?

The Rust Server Trends lists that take in SAKHALIN_ONLINE are: Rust community servers without the side modes and Vanilla Rust servers, recorded live. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.

Connecting

What steps get you onto SAKHALIN_ONLINE?

Enter client.connect 188.113.164.74:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^m,^v,gmrust,cs167584,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players 100 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167584
Build Game build: 167584.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^m
Monthly It wipes monthly, together with the Facepunch force wipe.

Difficulty

^v
Vanilla Unchanged from Facepunch's release: no altered rates, kits or rules.

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.

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.