Rust Server TrendsSeismic network · station log
Recording Stations11,681 Players34,835 Active2,855 Wipes · 3 h93 48 h

Station XX-10109 · no signal

{SEA} DESTINY | 2.5X | PVP |

Offline 148.113.3.215:26161 checked 1d ago

2.5x vanillamoddedoxide
Connect
Players now
1/ 75
1% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#10,109
top 45%
Last wipe
1d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-10109 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
1of 75 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Tue 19:00 UTC
Peak · 48 h
1most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
00.250.50.75118:0019:0020:0021:0022:00Wiped Tue 27 Oct, 20:50 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
010020030040018:0019:0020:0021:0022:00Wiped Tue 27 Oct, 20:50 UTCWIPE

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 6 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
15k10k15k20k6 Oct11 Oct15 Oct20 Oct24 Oct29 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
18.3 daysbetween real wipes
wipe-day peak
4players, last three wipes
crowd held
0%else halves by day 2

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 4, 2 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 27 Oct, 20:50 UTC1d ago – – – – running 1
Fri 9 Oct, 14:42 UTC19d ago M0.6rising 4 halved by day 2 18.3 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 EA · groups of 8+ · 2x · biweekly · 81 on average
29/ 115
Japan Tokyo - Limited Raid Hours |3x|PvP|JP EA · groups of 8+ · 3x · weekly · 40 on average
10/ 300
[SEA] Rust Manila 2x | Biweekly EA · groups of 8+ · 2x · biweekly · 25 on average
3/ 150
JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP EA · groups of 32+ · 5x · biweekly · 14 on average
10/ 120
[TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 EA · groups of 12+ · 5x · biweekly · 14 on average
3/ 200
Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|Long EA · groups of 100+ · 3x · monthly · 7 on average
7/ 120
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on {SEA} DESTINY | 2.5X | PVP |?

The procedural map on {SEA} DESTINY | 2.5X | PVP | is size 3,000 with seed 1627336182, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. The name of its map is Custom Map.

Which settings and rules apply on {SEA} DESTINY | 2.5X | PVP |?

Its name points to a gather rate of 2.5x on {SEA} DESTINY | 2.5X | PVP |. Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: unchanged from Facepunch's release: no altered rates, kits or rules. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on {SEA} DESTINY | 2.5X | PVP |?

{SEA} DESTINY | 2.5X | PVP | is not responding at this moment and is offline, last seen 28 hours ago. The seven-day average is 0 players, with a peak of 1. The last 48 hours show their highest activity at 18:00 UTC, averaging 1 players.

How does {SEA} DESTINY | 2.5X | PVP | rank against other Rust servers?

Over the last seven days, {SEA} DESTINY | 2.5X | PVP | recorded enough player hours to reach #10,109 worldwide, placing it in the top 45% of all ranked servers.

Operator and location

How reliably does {SEA} DESTINY | 2.5X | PVP | stay online?

As recorded now, {SEA} DESTINY | 2.5X | PVP | is not reachable, the last contact having been 28 hours ago. The uptime it reports puts its last restart about 14 minutes ago. 103 of 168 hours in the last 7 full days were up time, 61% of the total. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

How well does {SEA} DESTINY | 2.5X | PVP | perform under load?

The 48-hour average is 240 server fps; 240 is the lowest observed. At its highest, it carried 48,849 entities: buildings, deployables and the world's other contents. It reached a ceiling of 2,999 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is {SEA} DESTINY | 2.5X | PVP | hosted?

Its name points to Asia, but {SEA} DESTINY | 2.5X | PVP | publishes no region tag. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 148.113.3.215:26161 is the address it uses.

Which Rust version is {SEA} DESTINY | 2.5X | PVP | running?

{SEA} DESTINY | 2.5X | PVP | is running Rust network protocol 2635 and build 168909 on a machine with Linux. 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 {SEA} DESTINY | 2.5X | PVP |?

On average, the busiest point of its recent wipes drew 4 players. 2 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 2 it fell below half in the wipes where it didn't hold.

How often does {SEA} DESTINY | 2.5X | PVP | wipe, and on which days?

Too few wipes of {SEA} DESTINY | 2.5X | PVP | are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 29 hours is how long the current world has been running.

Server tags

What do the server tags on {SEA} DESTINY | 2.5X | PVP | mean?

The game's server browser reads the tags {SEA} DESTINY | 2.5X | PVP | publishes: gmrust (Game mode): The game mode is standard Rust survival; mp75 (Max players): Slots: 75; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does {SEA} DESTINY | 2.5X | PVP | appear?

The Rust Server Trends lists that take in {SEA} DESTINY | 2.5X | PVP | are: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.

Connecting

How do you connect to {SEA} DESTINY | 2.5X | PVP |?

Enter client.connect 148.113.3.215:26161 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://discord.com/invite/c8XuxmQv5P.

Instrument codes

Server tags

what each one means

Published as mp75,ptrak,$r?,v2635,^v,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp75
Max players Slots: 75.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Difficulty

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

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.