Online EA 15.235.160.24:60404 checked 9m ago
[SEA] Rust Manila 2x | Biweekly
Connect
srv = rust.server("15.235.160.24:60406")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 3% of all ranked servers, top 5% in EA. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 6h | Thu 12 Nov, 05:12 UTC | wipe |
| 2 | 27d 6h | Thu 26 Nov, 05:12 UTC | wipe |
| 3 | 34d 20h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 6h | Thu 10 Dec, 05:12 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 58, 41 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 05:12 UTC17h ago | NaN | NaN | running | 0 |
| 1 | Thu 15 Oct, 22:06 UTC14d ago | 58 | NaN | NaN | 8 |
| 2 | Thu 15 Oct, 04:53 UTC14d ago | 57 | NaN | 0.7 days | 0 |
| 3 | Thu 1 Oct, 18:45 UTC FW28d ago | 2 | held half | 13.4 days | 0 |
| 4 | Mon 21 Sep, 06:00 UTC38d ago | 3 | halved by day 1 | 10.5 days | 0 |
| 5 | 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 84 on average | 21/115 |
| 1 | [SEA] MayhemPH | 2x PvPvE | Raid 3PM-12AM | FULL WIPE 23/10 | EA · groups of 8+ · 2x · biweekly · 5 on average | 3/140 |
| 2 | [JP]初心者PVPサーバー|RaidTime・ Events | EA · groups of 10+ · biweekly · 14 on average | 1/100 |
| 3 | 瞌睡熊『5倍10废|10.30|萌新首选|无权限』 | EA · groups of 8+ · biweekly · 4 on average | 1/100 |
| 4 | [ASIA] RustSEA+|Xtra Modded|Pure PVE|2x|No Purge|EXP Leveling|E | EA · groups of 8+ · 2x · monthly · 2 on average | 1/50 |
| 5 | [JPN] Apple Server | PvP | Vanilla | 2Weekly | EA · groups of 8+ · biweekly · 2 on average | 1/50 |
Quick answers
From the figures on this page.
Population
What position does [SEA] Rust Manila 2x | Biweekly take in the server rankings?
Ranked #595 on seven-day player hours, [SEA] Rust Manila 2x | Biweekly is #26 in Asia and in the top 3% of all ranked servers.
How full does [SEA] Rust Manila 2x | Biweekly run?
Current row: 41 players on [SEA] Rust Manila 2x | Biweekly, against 150 slots. Over the last seven days it averaged 26 players and peaked at 114. Averaged by hour over 48 hours, 15:00 UTC is the busiest, at 111 players.
About the server
How well does [SEA] Rust Manila 2x | Biweekly perform?
The 48-hour average is 100 server fps, with a low of 50. The entity count peaked at 139,440, covering buildings, deployables and the rest of the world. A high of 4,605 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is [SEA] Rust Manila 2x | Biweekly on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by [SEA] Rust Manila 2x | Biweekly. Steam updates your game for you, but the protocol must match to join.
How reliable is [SEA] Rust Manila 2x | Biweekly, and is it up?
[SEA] Rust Manila 2x | Biweekly reports itself online at the current refresh. A restart about 15 hours ago is what its reported uptime implies. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
Where does [SEA] Rust Manila 2x | Biweekly sit?
With its EA tag, [SEA] Rust Manila 2x | Biweekly 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. 15.235.160.24:60404 is its address.
Map and rules
Which rules apply on [SEA] Rust Manila 2x | Biweekly, and what settings?
The name carries the figure: [SEA] Rust Manila 2x | Biweekly runs 2x gather. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC off.
What is the map on [SEA] Rust Manila 2x | Biweekly?
[SEA] Rust Manila 2x | Biweekly runs a procedural map of size 3,800 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Kabisera ng Pilipinas is what the map name field says.
Wipes and dates
When does [SEA] Rust Manila 2x | Biweekly wipe, and how often?
The prediction follows the tag, because [SEA] Rust Manila 2x | Biweekly's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 17 hours ago. The tags list a two-weekly wipe cycle.
On [SEA] Rust Manila 2x | Biweekly, what happens on wipe day?
Recent wipes averaged 39 players at their peak. 41 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 25% of recent wipes. In the wipes where it did not hold, half was lost by day 2.
Tags, lists
Which Rust Data filters and lists contain [SEA] Rust Manila 2x | Biweekly?
These Rust Data lists include [SEA] Rust Manila 2x | Biweekly: Modded Rust servers and 2x Rust servers. Under these filters on the server list, it is listed: 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.
How should you read the server tags on [SEA] Rust Manila 2x | Biweekly?
Read by the game's server browser, the tags [SEA] Rust Manila 2x | Biweekly publishes are: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): Slot count: 150; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EA (East Asia): East Asia is its listing in the server browser. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join [SEA] Rust Manila 2x | Biweekly?
The manual route: launch Rust, F1, then client.connect 15.235.160.24:60404. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://discord.com/invite/X4DyXjt5S.