RUST METRICSFlight deck · live data
Data live Servers11,686 Players34,855 Populated2,843 Fresh wipes 3 h96 Scan5 min
‹ All servers148.113.3.215:26161
Offline Full Queue Fresh wipe Wipe due No query

{SEA} DESTINY | 2.5X | PVP |

Offline 148.113.3.215:26161 checked 1d ago

2.5x vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Tue 22:00 UTC
0 19 38 56 75 PAX 1 /75

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 240 SERVER FPS

Server fps

48 h low 240 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 42,466 ×1000

Entities

48 h range 42,466–48,849 · memory 2,999 MB
1239 ET SINCE RESTART 00:14

Uptime

0 h 14 min since its last restart, at the last reading
7-day average0peak 1
Rank#10,109top 45%
Last wipe1d agono schedule published
Next wipe–too few wipes seen yet
Memory2,999MB48 h peak 1 players
REC 1

Players

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

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

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 gap18.3 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%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.

LOG

Wipes

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

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on {SEA} DESTINY | 2.5X | PVP |?

At their busiest, its recent wipes drew 4 players on average. After the latest wipe, numbers topped out at 2 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 2 when it didn't.

When does {SEA} DESTINY | 2.5X | PVP | wipe?

To tell the rhythm of {SEA} DESTINY | 2.5X | PVP |, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 28 hours ago the current world was made.

Lists and filters

How should you read the tags on {SEA} DESTINY | 2.5X | PVP |?

Tags published by {SEA} DESTINY | 2.5X | PVP |, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp75 (Max players): The server holds 75 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does {SEA} DESTINY | 2.5X | PVP | appear in Rust Metrics lists and filters?

These Rust Metrics lists carry {SEA} DESTINY | 2.5X | PVP |: Modded Rust servers, checked 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.

Population

Where does {SEA} DESTINY | 2.5X | PVP | sit in the rankings?

Ranking for {SEA} DESTINY | 2.5X | PVP |: #10,109 on seven-day player hours, top 45% of all ranked servers.

How full does {SEA} DESTINY | 2.5X | PVP | get?

Reading for {SEA} DESTINY | 2.5X | PVP |: offline at this moment; last seen 28 hours ago. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 18:00 UTC over the last 48 hours.

Server

Which location does {SEA} DESTINY | 2.5X | PVP | run from?

The name of {SEA} DESTINY | 2.5X | PVP | points to Asia, though it publishes no region tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 148.113.3.215:26161.

What Rust version is {SEA} DESTINY | 2.5X | PVP | on?

Reading: {SEA} DESTINY | 2.5X | PVP |, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

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

Check: fps. Average 240 server fps over the last 48 hours, low of 240. Within range. Check: entities. The peak was 48,849, counting buildings, deployables and the rest of the world. Memory peak: 2,999 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on {SEA} DESTINY | 2.5X | PVP |, and is it online?

{SEA} DESTINY | 2.5X | PVP | reports offline. The last reading came 28 hours ago. Reading: uptime. About 14 minutes ago it restarted, on its own count. Reading: 61% uptime over the last 7 full days. It was up 103 of 168 hours. Reading: first seen 6 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does {SEA} DESTINY | 2.5X | PVP | enforce, and what are its settings?

The name carries the rate: 2.5x gather on {SEA} DESTINY | 2.5X | PVP |. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. The server calls itself vanilla, with this meaning: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.

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

From seed 1627336182, the game generates the procedural map on {SEA} DESTINY | 2.5X | PVP |. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name Custom Map.

How to join

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

Check: join. Open Rust, press F1, then enter client.connect 148.113.3.215:26161. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/c8XuxmQv5P is where its website sits.

PLACARDS

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 plain Rust survival.
mp75
Max players The server holds 75 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Difficulty

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

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.