Rust Server TrendsSeismic network · station log
Recording Stations11,830 Players89,192 Active3,733 Wipes · 3 h415 48 h

Station EA-597 · recording

[SEA] Rust Manila 2x | Biweekly

Online EA 15.235.160.24:60404 checked 12m ago

2x biweekly wipes moddedoxide
Connect
Players now
49/ 150
33% full
Motion · 24 h
M1.7rising
+52 players on the day
7-day average
25
peak 114
Rank
#597
top 3% · #26 in EA
Last wipe
16h ago
biweekly schedule
Next wipe
6d 21h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station EA-597 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
49of 150 slots
Motion · 24 h
M1.7rising+52 players
Sharpest hour
−18into Thu 18:00 UTC
Peak · 48 h
114most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
05010015020022:0007:0016:0002:0011:0020:00Wiped Thu 29 Oct, 05:12 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
05010015020022:0007:0016:0002:0011:0020:00Wiped Thu 29 Oct, 05:12 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 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. The force wipe · high confidence

usual gap
10.5 daysbetween real wipes
on rhythm
20%of its recent wipes
wipe-day peak
39players, last three wipes
crowd held
25%else halves by day 2

Coming wipes

  1. 6d 21hThu 5 Nov, 19:00 UTCFW
  2. 13d 7hThu 12 Nov, 05:12 UTC
  3. 27d 7hThu 26 Nov, 05:12 UTC
  4. 34d 21hThu 3 Dec, 19:00 UTCFW
  5. 41d 7hThu 10 Dec, 05:12 UTC

The first 48 hours of its last wipes

Thu 15 OctThu 15 OctThu 1 Oct
020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 58, 41 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 29 Oct, 05:12 UTC16h ago – – – – running 0
Thu 15 Oct, 22:06 UTC13d ago M1.7rising 58 – – 8
Thu 15 Oct, 04:53 UTC14d ago M1.8rising 57 – 0.7 days 0
Thu 1 Oct, 18:45 UTC FW28d ago M0.3rising 2 held half 13.4 days 0
Mon 21 Sep, 06:00 UTC38d ago M0.5rising 3 halved by day 1 10.5 days 0
Mon 14 Sep, 06:01 UTC45d ago M0.0rising 1 halved by day 2 7 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 · 84 on average
20/ 115
[SEA] MayhemPH | 2x PvPvE | Raid 3PM-12AM | FULL WIPE 23/10 EA · groups of 8+ · 2x · biweekly · 5 on average
2/ 140
[JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 14 on average
1/ 100
瞌睡熊『5倍10废|10.30|萌新首选|无权限』 EA · groups of 8+ · biweekly · 4 on average
1/ 100
[ASIA] RustSEA+|Xtra Modded|Pure PVE|2x|No Purge|EXP Leveling|E EA · groups of 8+ · 2x · monthly · 2 on average
0/ 50
[JP/PvE][BPリサーチ]MatoyServer初しん者〇 EA · groups of 8+ · biweekly · 2 on average
1/ 50
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [SEA] Rust Manila 2x | Biweekly?

The procedural map on [SEA] Rust Manila 2x | Biweekly is size 3,800 with seed 1337, 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 Kabisera ng Pilipinas.

Which settings and rules apply on [SEA] Rust Manila 2x | Biweekly?

2x gather is what [SEA] Rust Manila 2x | Biweekly runs, judging by its name. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is off: VAC, from Valve.

Live population

How many players are recorded on [SEA] Rust Manila 2x | Biweekly right now?

49 of the 150 slots on [SEA] Rust Manila 2x | Biweekly are filled right now. Averaged across the last seven days the population was 25 players, reaching a peak of 114. The last 48 hours show their highest activity at 15:00 UTC, averaging 111 players.

How does [SEA] Rust Manila 2x | Biweekly rank against other Rust servers?

[SEA] Rust Manila 2x | Biweekly is #26 in Asia and #597 worldwide on the past week's player hours, within the top 3% of ranked servers.

Server details

How reliably does [SEA] Rust Manila 2x | Biweekly stay online?

As recorded now, [SEA] Rust Manila 2x | Biweekly is running. Its reported uptime points to a restart about 14 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does [SEA] Rust Manila 2x | Biweekly perform under load?

Across the last 48 hours it averaged 100 server fps, with a floor of 50. Buildings, deployables and all the rest of the world's entities brought it to a high of 139,440. It reached a ceiling of 4,605 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Which region does [SEA] Rust Manila 2x | Biweekly run from?

With its EA tag, [SEA] Rust Manila 2x | Biweekly lists itself in Asia. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 15.235.160.24:60404.

What build of Rust does [SEA] Rust Manila 2x | Biweekly use?

On Linux, [SEA] Rust Manila 2x | Biweekly runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on [SEA] Rust Manila 2x | Biweekly?

39 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 41 hours after the wipe. Until the next wipe the crowd remained above half that peak in 25% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 2.

On what timetable does [SEA] Rust Manila 2x | Biweekly run its wipes?

Its schedule cannot be confirmed, as too few of [SEA] Rust Manila 2x | Biweekly's wipes are on record; the prediction follows its tag instead. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 16 hours is how long the current world has been running. In its tags it sets out a wipe schedule of every two weeks.

Tags

What do the server tags on [SEA] Rust Manila 2x | Biweekly mean?

The game's server browser reads the tags [SEA] Rust Manila 2x | Biweekly publishes: gmrust (Game mode): You'll find standard Rust survival here; mp150 (Max players): 150 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^b (Biweekly): A wipe comes every second week; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EA (East Asia): The server browser files it under East Asia. 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] Rust Manila 2x | Biweekly appear?

You will find [SEA] Rust Manila 2x | Biweekly on the following Rust Server Trends lists: 2x Rust servers, listed live and Modded Rust servers, tracked live. On the server list, the filters it matches are: 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 24 hours; Gather rate: 2x; Players now: At least 10; Average players: 25+ on average.

Join the server

What steps get you onto [SEA] Rust Manila 2x | Biweekly?

To join, enter client.connect 15.235.160.24:60404 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://discord.com/invite/X4DyXjt5S.

Instrument codes

Server tags

what each one means

Published as mp150,ptrak,$r?,v2635,^b,EA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp150
Max players 150 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly A wipe comes every second week.

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.

Region

EA
East Asia The server browser files it 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.

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.