Rust Server TrendsSeismic network · station log
Recording Stations11,670 Players57,098 Active3,402 Wipes · 3 h98 48 h

Station EA-15399 · no signal

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

Offline EA 1.162.59.17:28015 checked 6d ago

5x biweekly wipes moddedoxide
Connect
Players now
0/ 200
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,399
top 69% · #501 in EA
Last wipe
12d ago
biweekly schedule
Next wipe
1d 23h
Fri 30 Oct, 10:14 UTC
Seismic record · station EA-15399 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 200 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
[TW-JP-KR-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 EA · groups of 12+ · 5x · biweekly · 14 on average
7/ 200
JumpRust.com - 戦え! 5x|JP/SEA|PVP+PVE|Events|Shop|Kits|TP EA · groups of 32+ · 5x · biweekly · 13 on average
28/ 120
ASIA | RPG · Skills · NEW | Casual PvP | 2-5x | Wiped 10/22 EA · groups of 8+ · 5x · weekly · 3 on average
3/ 120
EKKK PVP 5X 愉快生存伺服器 EA · groups of 8+ · 5x · 2 on average
4/ 150
#2[搞就完了]新開|10X|秒造快燒|龍爭虎鬥 EA · groups of 8+ · 10x · biweekly · 1 on average
1/ 60
[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 EA · groups of 8+ · 2x · biweekly · 78 on average
138/ 165
Readings, in words

Quick answers

from the figures on this page

Server rules

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

[TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 uses a procedural map, which the game generates.

Which settings and rules apply on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16?

5x gather is what [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 runs, judging by its name. Up to 12 players can be in a group. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 right now?

No players are recorded on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 at this moment; it is offline, and the last sighting was 6 days 8 hours ago. Averaged across the last seven days, the population was 0 players.

How does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 rank against other Rust servers?

For player hours across the last seven days, [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 takes #15,399 overall and #501 in Asia, inside the top 69% of all ranked servers.

Server facts

How reliably does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 stay online?

[TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 is down at the moment; the last recorded contact was 6 days 8 hours ago. Of the 120 hours in the last 5 full days, it was up for 0, or 0% of the time. 22 October 2026 is when Rust Server Trends first recorded it.

Which region does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 run from?

The EA tag is how [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 lists itself in Asia. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 1.162.59.17:28015 is the address it uses.

What build of Rust does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 use?

On Windows, [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

How often does [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 wipe, and on which days?

From biweekly: 14 days after its last wipe the next wipe of [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 is estimated. The date of its next wipe is Friday 30 October at 10:14 UTC. The present world dates from 12 days. Its tags state that it wipes every two weeks.

Server tags

What do the server tags on [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 mean?

The game's server browser reads the tags [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 publishes: gmrust (Game mode): You'll find standard Rust survival here; mp200 (Max players): Slots: 200; ts12 (Group limit): The team limit is 12; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): East Asia is the region it's listed under in the browser. 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 [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 appear?

The Rust Server Trends lists that take in [TW-JP-SEA] Metaverse 5X | PVP | MAP WIPE 10/16 are: 5x Rust servers and Modded Rust servers, tracked live. You will find it 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.

How to join

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

Enter client.connect 1.162.59.17: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 mp200,ptrak,$r?,v2634,^b,EA,gmrust,cs167781,ts12,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp200
Max players Slots: 200.
ts12
Group limit The team limit is 12.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167781
Build The game build is 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Mods and access

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

Region

EA
East Asia East Asia is the region it's listed under in the browser.

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.