[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly
Online EA 148.113.24.99:29029 checked 5m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 39% of all ranked servers, top 78% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 12:33 UTC, in 6h. Its biweekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 6h | Thu 29 Oct, 12:33 UTC | its own |
| 7d 13h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 14d 6h | Thu 12 Nov, 12:33 UTC | its own |
| 28d 6h | Thu 26 Nov, 12:33 UTC | its own |
| 35d 13h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 42d 6h | Thu 10 Dec, 12:33 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 12:33 UTC13d ago | 1 | – | running | 0 |
| Thu 1 Oct, 18:38 UTC FW27d ago | 2 | halved by day 2 | 13.7 days | 0 |
| Sun 27 Sep, 08:58 UTC31d ago | 1 | halved by day 2 | 4.4 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 82 on average | 49 / 115 |
| [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 24 on average | 28 / 150 |
| [SEA] MayhemPH | 2x PvPvE | Raid 3PM-12AM | FULL WIPE 23/10 | EA · groups of 8+ · 2x · biweekly · 4 on average | 4 / 140 |
| ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 16 on average | 5 / 100 |
| [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 | EA · no group limit · biweekly · 4 on average | 0 / 20 |
| 瞌睡熊『5倍10废|10.29|萌新首选|无权限』 | EA · groups of 8+ · biweekly · 4 on average | 4 / 100 |
Quick answers
from the figures on this pageWipe cycle
When does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly wipe?
The tag sets the prediction: too few of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly's wipes are on record to confirm its schedule. Thursday 29 October at 12:33 UTC is when its next wipe is due. The world now in play was created 13 days 17 hours ago. A wipe every two weeks is stated in its tags.
Wipe day on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly: what should you expect?
The average busiest count over recent wipes is 1 players. 2 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 0% of cases. By day 2 it had fallen below half where the hold failed.
Server details
What is the hosting location of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Its EA tag puts [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly in Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 148.113.24.99:29029.
What Rust build does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly run?
Rust network protocol 2635 and build 168909 on Linux is the setup for [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly. Joining requires the same protocol on your game; Steam handles the update.
Is [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly up, and how steady is its uptime?
The current status of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly is online. The uptime it reports puts the last restart at about 4 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. It entered Rust Server Analytics records on 27 September 2026.
Does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly perform well?
Over 48 hours the average held at 232 server fps, and the minimum was 79. At its highest the entity count was 51,372, including buildings, deployables and all else. At its highest, memory use was 3,213 MB. Players experience lag as low fps combined with a rising entity count.
Lists and tags
How should the tags on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly be read?
gmrust (Game mode): Rust survival, standard ruleset; mp40 (Max players): Capacity of 40 slots; ts8 (Group limit): Default team size of 8; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^b (Biweekly): Every two weeks the server wipes; ^v (Vanilla): Facepunch's game unchanged: no altered rates, kits or rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia are the tags [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly publishes, and the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Where does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly fits are: Rust servers with a 2x gather rate and Modded Rust servers: live data. It appears on the server list under the following filters: Region: Asia; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
Population
Where does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly sit among Rust servers?
[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly holds #8,704 on seven-day player hours and #437 in Asia, inside the top 39% of the ranked field.
What is the population of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Population at the current refresh: 0 players on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly, against 40 slots. Seven-day figures: an average of 0 players and a peak of 1.
Map and rules
What settings and rules does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly use?
[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly names a 2x gather rate. The game's default 8-player group limit is in force. survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. Vanilla is its own description: facepunch's game unchanged: no altered rates, kits or rules. The server runs with VAC, Valve's anti-cheat, enabled.
What is the map for [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly uses a procedural map of size 3,000 with seed 1614537442, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here.
How to join
How can a player join [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
In the Rust console (F1), enter client.connect 148.113.24.99:29029. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://rust.nexnise.com/ is its website.