RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,212 Populated3,932 Fresh wipes 3 h403 Scan5 min
‹ All servers15.235.160.24:60404
Online Full Queue Fresh wipe Wipe due No query

[SEA] Rust Manila 2x | Biweekly

Online EA 15.235.160.24:60404 checked 9m ago

2x biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 16:00 UTC
0 38 75 112 150 PAX 89 /150

Players now

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

Server fps

48 h low 60 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 101,753 ×1000

Entities

48 h range 77,207–141,741 · memory 3,702 MB
1239 ET SINCE RESTART 10:39

Uptime

10 h 39 min since its last restart, at the last reading
7-day average24peak 114
Rank#604top 3% · #25 in EA
Last wipe12h agobiweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Memory3,702MB48 h peak 114 players
REC 1

Players

AveragePeakWipe
05010015020018:0003:0012:0022:0007:0016:00Wiped Thu 29 Oct, 05:12 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020018:0003:0012:0022:0007:0016: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.

REC 3

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.

PLAN

Wipe schedule

from its schedule tag

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

usual gap10.5 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak39players, last three wipes
crowd held25%else halves by day 2

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 1hFW
  2. WPT 2Thu 12 Nov, 05:12 UTC13d 11h
  3. WPT 3Thu 26 Nov, 05:12 UTC27d 11h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 1hFW
  5. WPT 5Thu 10 Dec, 05:12 UTC41d 11h

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 05:12 UTC12h ago – – running 0
Thu 15 Oct, 22:06 UTC13d ago 58 – – 8
Thu 15 Oct, 04:53 UTC14d ago 57 – 0.7 days 0
Thu 1 Oct, 18:45 UTC FW27d ago 2 held half 13.4 days 0
Mon 21 Sep, 06:00 UTC38d ago 3 halved by day 1 10.5 days 0
Mon 14 Sep, 06:01 UTC45d ago 1 halved by day 2 7 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 happens on [SEA] Rust Manila 2x | Biweekly when wipe day comes?

An average of 39 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 41 hours in. The crowd stayed above half that peak until the next wipe in 25% of its recent wipes. It fell below half by day 2 when it didn't.

When does [SEA] Rust Manila 2x | Biweekly wipe?

The prediction follows its tag, because too few of [SEA] Rust Manila 2x | Biweekly's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 12 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tag meanings

How should you read the tags on [SEA] Rust Manila 2x | Biweekly?

Tags published by [SEA] Rust Manila 2x | Biweekly, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): 150 slots in total; 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): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EA (East Asia): East Asia is the browser category it sits in. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show [SEA] Rust Manila 2x | Biweekly?

These Rust Metrics lists carry [SEA] Rust Manila 2x | Biweekly: 2x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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 50; Average players: 10+ on average.

Player count

Where does [SEA] Rust Manila 2x | Biweekly sit in the rankings?

Player hours over the last seven days put [SEA] Rust Manila 2x | Biweekly at #604, #25 in Asia, in the top 3% of all ranked servers.

What is the population on [SEA] Rust Manila 2x | Biweekly?

89 of 150 slots are filled on [SEA] Rust Manila 2x | Biweekly right now. Check: players over seven days. Average 24, peak 114. The last 48 hours peaked at 15:00 UTC, averaging 111 players at that hour.

Server details

What location is [SEA] Rust Manila 2x | Biweekly hosted in?

Reading: location. The EA tag puts [SEA] Rust Manila 2x | Biweekly in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 15.235.160.24:60404.

What Rust version is [SEA] Rust Manila 2x | Biweekly on?

Rust network protocol 2635 and build 168909 on Linux is the build [SEA] Rust Manila 2x | Biweekly runs. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on [SEA] Rust Manila 2x | Biweekly within range?

Check: fps. Average 102 server fps over the last 48 hours, low of 60. Within range. Check: entities. The peak was 141,741, counting buildings, deployables and the rest of the world. Memory peak: 4,425 MB. What players call lag comes from low fps and an entity count on the rise.

Is [SEA] Rust Manila 2x | Biweekly up, and how often does it stay up?

[SEA] Rust Manila 2x | Biweekly reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 10 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What rules does [SEA] Rust Manila 2x | Biweekly enforce, and what are its settings?

Gather rate check: 2x. That comes from the name [SEA] Rust Manila 2x | Biweekly. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is off.

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

Check: map. Procedural, size 3,800, seed 1337, generated by the game on [SEA] Rust Manila 2x | Biweekly. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name Kabisera ng Pilipinas.

Join

How can you get onto [SEA] Rust Manila 2x | Biweekly?

To join: start Rust, press F1 and type client.connect 15.235.160.24:60404. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/X4DyXjt5S is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp150
Max players 150 slots in total.
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 Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

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

Region

EA
East Asia East Asia is the browser category it sits in.

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.