Rust Data

rustdata.spaceservers1.162.59.17:28016.ipynb

Run all rust-data · live

‹ All servers

Offline EA 1.162.59.17:28015 checked 6d ago

[TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16

5x biweekly wipes moddedoxide

Connect

srv = rust.server("1.162.59.17:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/200 # 0% full
7-day average 0 # peak –
rank #15,349 # top 69% · #501 in EA
last wipe 12d ago # biweekly schedule
next wipe 1d 9h # Fri 30 Oct, 10:14 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 69% of all ranked servers, top 89% in EA. Ranked on player hours over the last seven days.

Wipe schedule

srv.wipe_schedule()

Next wipe Friday 30 October, 10:14 UTC, in 1d 9h. # Biweekly: 14 days after its last wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · no wipe seen yet.

# 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
1.162.59.17:28015
region
EA
max players
200
group limit
12 max
wipe schedule
biweekly
last wipe
16 Oct 2026, 10:14 UTC
hostname
–
first seen
22 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TPEA · groups of 32+ · 5x · biweekly · 14 on average4/120
1[TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16EA · groups of 12+ · 5x · biweekly · 14 on average1/200
2ASIA | RPG · Skills · NEW | Casual PvP | 2-5x | Wiped 10/22EA · groups of 8+ · 5x · weekly · 3 on average3/120
3EKKK PVP 5X 愉快生存伺服器EA · groups of 8+ · 5x · 2 on average1/150
4[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10EA · groups of 8+ · 2x · biweekly · 81 on average8/115
5[SEA] Rust Manila 2x | BiweeklyEA · groups of 8+ · 2x · biweekly · 25 on average1/150

Quick answers

From the figures on this page.

Population

What position does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 take in the server rankings?

Player hours over the last seven days: #15,349 for [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16, #501 in Asia, within the top 69% of the ranked set.

What population does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 carry?

The current row shows [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 offline; the last response was 6 days 22 hours ago. Over the last seven days it averaged 0 players.

Server data

What is the Rust version on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16?

Rust network protocol 2634 and build 167781 on Windows is what [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 runs. Steam updates your game for you, but the protocol must match to join.

How reliable is [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16, and is it online now?

Offline now for [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16, last seen 6 days 22 hours ago. Uptime of 0% across the last 6 full days: 0 hours of 144. Rust Data logged it first on 22 October 2026.

Where does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 sit?

With its EA tag, [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 lists itself in Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 1.162.59.17:28015.

Map and rules

What rules and settings are recorded for [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16?

The name carries the figure: [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 runs 5x gather. 12 players is the maximum per group. Recorded as survival, 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. VAC, Valve's anti-cheat, is enabled.

What is the map on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16?

A procedural map runs on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16, generated by the game.

Wipes and dates

When does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 wipe, and on what schedule?

An estimate from biweekly: 14 days after its last wipe gives [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16's next wipe. On Friday 30 October at 10:14 UTC the next wipe is due. The world it runs now was generated 12 days 14 hours ago. The tags list a two-weekly wipe cycle.

Tags, lists

Where does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 appear among Rust Data lists and filters?

These Rust Data lists include [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16: Modded Rust servers and Rust servers filtered by gather rate: 5x. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 5x.

Which meanings do the tags on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 hold?

Read by the game's server browser, the tags [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 publishes are: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts12 (Group limit): The team cap is 12; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): In the server browser it sits under East Asia. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16?

In Rust, F1 opens the console: type client.connect 1.162.59.17:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp200,ptrak,$r?,v2634,^b,EA,gmrust,cs167781,ts12,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp200
Max players Slot count: 200.
ts12
Group limit The team cap is 12.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

EA
East Asia In the server browser it sits under East Asia.

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 48,039 players 11,719 servers online