[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly
Online EA 148.113.24.99:29029 checked 11m ago
Server instruments
last reading Thu 15:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 226 · below 20 is lag, below 10 is badEntities
48 h range 48,757–51,372 · memory 2,986 MBUptime
15 h 45 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 37% of all ranked servers, top 76% in EA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 2hFW
- WPT 2Thu 12 Nov, 12:33 UTC13d 19h
- WPT 3Thu 26 Nov, 12:33 UTC27d 19h
- WPT 4Thu 3 Dec, 19:00 UTC35d 2hFW
- WPT 5Thu 10 Dec, 12:33 UTC41d 19h
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 UTC14d 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 UTC32d 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- 50/115
- 105/150
- 6/140
- 9/100
- 1/20
- 4/100
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 2 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 2 it fell below half.
What wipe timing does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly follow?
Its tag guides the prediction: too few of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | 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. The world in play was created 14 days 4 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.
Tag meanings
How should you read the tags on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Tags published by [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): Slots: 40; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe schedule; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server; 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 [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Rust Metrics lists featuring [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly: 2x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under 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; Gather rate: 2x.
Player count
What position does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly hold among Rust servers?
Top 37% of all ranked servers: [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly takes #8,168 on seven-day player hours and #407 in Asia.
What is the population on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Current headcount on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly: 0 players, 40 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 11:00 UTC, 1 players on average.
Server
Where does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly sit?
[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly gives Asia as its location, with the EA tag. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 148.113.24.99:29029.
What Rust version is [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly on?
Rust network protocol 2635 and build 168909 on Linux is the build [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly runs. Matching protocol is required to join. Let Steam update your game.
Is performance on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly within range?
Reading: 234 server fps on average across the last 48 hours. It never dropped below 226. Check: entities. The peak was 51,372, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,479 MB. What players call lag comes from low fps and an entity count on the rise.
Is [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly up, and how often does it stay up?
Check: connection. [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly is online at this moment. By its reported uptime, the last restart was roughly 15 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 27 September 2026.
Settings and map
What settings and rules apply on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Gather rate check: 2x. That comes from the name [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Check: anti-cheat. VAC, Valve's system, is on.
What map is [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly on?
From seed 1614537442, the game generates the procedural map on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map.
Connection
How can you get onto [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?
Press F1 in Rust and enter client.connect 148.113.24.99:29029. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://rust.nexnise.com/ is where its website sits.