Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO Q SRV11,700online PAX38,808playing OCC2,943with players WIPED 3H91
MODModded traffic
Callsign

IND8706=

[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly

Online EA 148.113.24.99:29029 checked 10m ago

2x biweekly wipes vanillamoddedoxide
Clearance · join
Players now 0/ 40 0% full
7-day average0peak 1
Rank#8,706top 39% · #438 in EA
Last wipe13d agobiweekly schedule
Next wipe10hThu 29 Oct, 12:33 UTC
Track history

Players

AveragePeak
0123403:0012:0021:0005:0014:0000:00

Hourly average and peak, UTC.

Server performance

010020030040003:0012:0021:0005:0014:0000:00

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 best
RankRank in region
15k10k15k20k27 Sep3 Oct10 Oct16 Oct23 Oct29 Oct

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

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 29 October, 12:33 UTC, in 10h.

Its biweekly schedule tag · low confidence

usual gap9.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 2

Coming wipes

  1. 10hThu 29 Oct, 12:33 UTC
  2. 7d 16hThu 5 Nov, 19:00 UTCFW
  3. 14d 10hThu 12 Nov, 12:33 UTC
  4. 28d 10hThu 26 Nov, 12:33 UTC
  5. 35d 16hThu 3 Dec, 19:00 UTCFW
  6. 42d 10hThu 10 Dec, 12:33 UTC

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctSun 27 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign SEA000EA · groups of 8+ · 2x · biweekly · 81 on average [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10
    Players 20/115
  2. 02MOD
    Callsign SEA406EA · groups of 8+ · 2x · biweekly · 25 on average [SEA] Rust Manila 2x | Biweekly
    Players 3/150
  3. 03MOD
    Callsign SEA017EA · groups of 8+ · 2x · biweekly · 4 on average [SEA] MayhemPH | 2x PvPvE | Raid 3PM-12AM | FULL WIPE 23/10
    Players 4/140
  4. 04MOD
    Callsign EVN020EA · groups of 10+ · biweekly · 17 on average [JP]初心者PVPサーバー|RaidTime・ Events
    Players 1/100
  5. 05MOD
    Callsign ONL015EA · no group limit · biweekly · 4 on average [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29
    Players 2/20
  6. 06MOD
    Callsign SRV016EA · groups of 8+ · biweekly · 4 on average 瞌睡熊『5倍10废|10.29|萌新首选|无权限』
    Players 1/100
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

2x Rust servers, tracked live and Modded servers, tracked live — the Rust Tracker lists that include [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly. These filters surface it on the server list: 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.

How should you read the tags on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Listed for the server browser to read, [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly publishes these tags: gmrust (Game mode): Rust survival, standard mode; mp40 (Max players): Capacity: 40 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): As Facepunch ships it: rates, kits and rules are unchanged; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings; EA (East Asia): The server browser lists it under East Asia. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

What should you expect on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly when wipe day lands?

The average peak across recent wipes: 1 players. 2 hours after the latest wipe, the crowd peaked. Half the peak was held until the next wipe in 0% of its recent wipes. The fall below half came by day 2 where it did not hold.

When does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly wipe?

The prediction for [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly follows its tag, as too few wipes are on record to confirm the schedule. Thursday 29 October at 12:33 UTC is when the next wipe falls due. Its world went live 13 days 13 hours. Its tags carry an every-two-weeks wipe schedule.

Server Details

What is the uptime on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly, and is it online?

[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly is up and online at this moment. About 46 minutes ago it restarted last, based on reported uptime. 167 of 168 hours up over the last 7 full days: 99% uptime. First contact for Rust Tracker: 27 September 2026.

Which Rust version is confirmed on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Rust network protocol 2635 and build 168909 is the build on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly; the platform is Linux. Steam updates it for you; your game must share the protocol to join.

Is [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly holding performance?

Server fps held an average of 232 across the last 48 hours, never below 79. Maximum entities carried: 51,321, from buildings and deployables to everything else. Peak memory use: 3,213 MB. A climbing entity count and low fps are what register as lag for players.

Where does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly sit?

The EA tag places [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly in Asia, by its own listing. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 148.113.24.99:29029.

Population

How many players are on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly right now?

Tracking [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly: 0 of 40 slots filled. Seven-day average 0 players; peak 1.

Where does [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly sit in the server rankings?

[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly places #8,706 on seven-day player hours, #438 in Asia and in the top 39% of all ranked servers.

Map and Rules

Which settings and rules are confirmed on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

The name says it: [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly runs 2x gather. The game's default applies: groups can have up to 8 players. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. Vanilla is its own label: as Facepunch ships it: rates, kits and rules are unchanged. VAC is on, Valve's anti-cheat.

Which map is confirmed for [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Generated by the game from seed 1614537442, the procedural map on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly measures 3,000. Size and seed match, so the map is the same: view it on RustMaps from this page.

How to Join

Which steps join [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Open the console in Rust with F1 after starting the game, then type client.connect 148.113.24.99:29029. Alternatively, Launch Rust here opens Rust via Steam and connects you. The server's website: https://rust.nexnise.com/.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp40
Max players Capacity: 40 slots.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla As Facepunch ships it: rates, kits and rules are unchanged.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Under Modded: the game is changed by plugins or settings.

Region

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