Rust Data

rustdata.spaceservers148.113.3.215:26162.ipynb

Run all rust-data · live

‹ All servers

Offline 148.113.3.215:26161 checked 1d ago

{SEA} DESTINY | 2.5X | PVP |

2.5x vanillamoddedoxide

Connect

srv = rust.server("148.113.3.215:26162")
print(srv.connect_command)

Right now

srv.summary()
players now 1/75 # 1% full
7-day average 0 # peak 1
rank #10,116 # top 45%
last wipe 1d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75118:0019:0020:0021:0022:00Wiped Tue 27 Oct, 20:50 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 20:50 UTC1d ago NaN NaN running 1
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.

display(srv.map, srv.info())

Map

3000 · seed 1627336182
Map of {SEA} DESTINY | 2.5X | PVP |
map
Custom Map
size
3000
seed
1627336182

Server

srv.info()
address
148.113.3.215:26161
region
–
max players
75
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 22:22 UTC
hostname
–
first seen
6 Oct 2026

About this server · in its own words

print(srv.description)
[SEA] DESTINY | 2.5X | PVP| 3 Player Team Limit 2.5X Gather Farming Oping in 29 Oct PvP • Raiding • Competitive Gameplay No scripet - No cheat

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 82 on average44/115
1Japan Tokyo - Limited Raid Hours |3x|PvP|JPEA · groups of 8+ · 3x · weekly · 40 on average10/300
2[SEA] Rust Manila 2x | BiweeklyEA · groups of 8+ · 2x · biweekly · 24 on average0/150
3JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TPEA · groups of 32+ · 5x · biweekly · 14 on average10/120
4[TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16EA · groups of 12+ · 5x · biweekly · 14 on average3/200
5Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|LongEA · groups of 100+ · 3x · monthly · 7 on average7/120

Quick answers

From the figures on this page.

Population data

How does {SEA} DESTINY | 2.5X | PVP | compare in the rankings?

Over the last seven days {SEA} DESTINY | 2.5X | PVP | sits at #10,116 on player hours, in the top 45% of ranked servers.

How many players does {SEA} DESTINY | 2.5X | PVP | hold at once?

The current row shows {SEA} DESTINY | 2.5X | PVP | offline; the last response was 30 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 18:00 UTC, mean 1 players.

Server data

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

The 48-hour average is 240 server fps, with a low of 240. Entity numbers reached 48,849, and that includes buildings, deployables and the rest. The memory field tops out at 2,999 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does {SEA} DESTINY | 2.5X | PVP | run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by {SEA} DESTINY | 2.5X | PVP |. Steam updates your game for you, but the protocol must match to join.

How reliable is {SEA} DESTINY | 2.5X | PVP |, and is it up?

The latest sample has {SEA} DESTINY | 2.5X | PVP | offline, with a last sighting 30 hours ago. The uptime it reports puts the last restart about 14 minutes ago. Uptime of 61% across the last 7 full days: 103 hours of 168. The first row Rust Data holds for it is dated 6 October 2026.

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

No region tag is published by {SEA} DESTINY | 2.5X | PVP |, though its name points to Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 148.113.3.215:26161 is its address.

Map and rules

What rules and settings are recorded for {SEA} DESTINY | 2.5X | PVP |?

The name carries the figure: {SEA} DESTINY | 2.5X | PVP | runs 2.5x gather. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. VAC is running: Valve's anti-cheat is on.

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

{SEA} DESTINY | 2.5X | PVP | runs a procedural map of size 3,000 with seed 1627336182, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.

Wipe data

On what schedule does {SEA} DESTINY | 2.5X | PVP | wipe?

A rhythm cannot be read from the wipes of {SEA} DESTINY | 2.5X | PVP | on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 30 hours ago.

On {SEA} DESTINY | 2.5X | PVP |, what happens on wipe day?

Recent wipes averaged 4 players at their peak. 2 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 2 in the other cases.

Tags and filters

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

On Rust Data, {SEA} DESTINY | 2.5X | PVP | appears in these lists: Modded Rust servers. It appears under these filters 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.

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

These tags are published by {SEA} DESTINY | 2.5X | PVP | and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): Slot count: 75; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into {SEA} DESTINY | 2.5X | PVP |?

In Rust, F1 opens the console: type client.connect 148.113.3.215:26161. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://discord.com/invite/c8XuxmQv5P.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp75
Max players Slot count: 75.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Difficulty

^v
Vanilla Facepunch's stock game, with rates, kits and rules untouched.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change 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.

Rust Data 30,176 players 11,635 servers online