Skip to the page
RUST ANALYTICS
LIVE35,650PLY11,449SRV
QUOTE 148.113.24.99:29029 Online EA checked 9m ago

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

2x biweekly wipes vanillamoddedoxide
Players · last
0/ 40
+024h
0% full
7-day avg 0 peak 1
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
0/ 40
0% full
Change · 24h
+0
no reading a day ago
7-day average
0
peak 1
Rank
#12,941
top 58% · #470 in EA
Rank · 7d ago
#12,298
643 places down
Last wipe
13d ago
biweekly schedule
Next wipe
15h
Thu 15 Oct, 18:38 UTC
Group limit
8
8, the default
Gather rate
2x
read from the name
Score
2
player hours, last seven days
Map
3000
Procedural Map · seed 69420
First seen
27 Sep 2026
no hostname published

Players

AveragePeak
0123404:0013:0022:0008:0017:0002:00

Hourly average and peak, UTC.

Server performance

010020030040004:0013:0022:0008:0017:0002: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 Sep1 Oct4 Oct8 Oct11 Oct15 Oct

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

Wipe schedule

from its schedule tag
Next wipeThursday 15 October, 18:38 UTCin 15h

Its biweekly schedule tag · low confidence

usual gap
4.4 days
between real wipes
wipe-day peak
2
players, last three wipes
crowd held
0%
else halves by day 2

Coming wipes

  1. 15hThu 15 Oct, 18:38 UTC
  2. 14d 15hThu 29 Oct, 18:38 UTC
  3. 21d 15hThu 5 Nov, 19:00 UTCFW
  4. 28d 15hThu 12 Nov, 18:38 UTC
  5. 42d 15hThu 26 Nov, 18:38 UTC

The first 48 hours of its last wipes

Thu 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 2, 26 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 18:38 UTC FW13d ago 2 – running 0
Sun 27 Sep, 08:58 UTC17d 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1[SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 13/10EA · groups of 8+ · 2x · biweekly · 74 on average21/115−31−59.4%
2[SEA] Rust Manila 2x | BiweeklyEA · groups of 8+ · 2x · biweekly · 4 on average0/150−1
3JP 社会人 SOLO Chill 2x NoTeamsEA · groups of 8+ · 2x · biweekly · 2 on average2/20+1+60.0%
4[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 5 on average0/100−2−100.0%
5[ASIA] RustSEA+|Xtra Modded|Pure PVE|2x|No Purge|EXP Leveling|EEA · groups of 8+ · 2x · monthly · 5 on average5/50+0+5.3%
6VandalRust|JP/KR/SEA|2X|Raid Hours|初心者歓迎|金曜日EA · groups of 8+ · 2x · weekly · 4 on average4/100−1−20.0%

Quick answers

from the figures on this page

Map and Rules

What settings and rules are in place on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly carries its gather rate in its name: 2x. Up to 8 players per group, which is the game's default. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are running. It uses the term vanilla for itself: no altered rates, kits or rules: the game as Facepunch ships it. VAC is active.

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

[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly uses a procedural map of size 3,000 with seed 69420, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.

Player Count

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

On seven-day player hours, [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly sits at #12,941, in the top 58% across ranked servers and #470 in Asia.

What is the population on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

On [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly, 0 players are in now, out of 40 slots. The seven-day average is 0 players, with a peak of 1.

Wipe Cycle

What happens on wipe day at [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Recent wipes at this server drew an average peak of 2 players. 26 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 0% of its recent wipes. The crowd fell below half by day 2 when it did not hold.

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

The prediction follows the tag because too few of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly's wipes are on record to confirm its schedule. On Thursday 15 October at 18:38 UTC the next wipe is due. Its world now is 13 days 8 hours old. The tags show wipes every two weeks.

Server Overview

What is the location of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

With the EA tag, [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly lists itself in Asia. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 148.113.24.99:29029.

What is the performance like on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Server fps over the last 48 hours: 238 on average, 226 at the lowest. At its peak it held 48,428 entities: buildings, deployables and the rest of the world. The memory ceiling reached 3,580 MB. Low fps and growing entities are the source of felt lag.

[IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly runs which version of Rust?

The build is Rust network protocol 2634 and build 167781 on Linux, running on [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly. Joining requires the same protocol on your game, which Steam updates.

What is the uptime and reliability of [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Online at this moment: [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly. The reported uptime puts its last restart at about 2 hours ago. The last 7 full days give 98% uptime, 164 hours on out of 168. 27 September 2026 is when Rust Analytics first saw it.

Tags & Filters

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

The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp40 (Max players): Capacity: 40 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^b (Biweekly): Two-week wipe cycle; ^v (Vanilla): No altered rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded listing applies: plugins or settings change play; EA (East Asia): The server browser files it under East Asia, which [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly publishes. Also in the tags and at the top of this page: current players, queue and world creation time.

On Rust Analytics, which lists and filters feature [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

On Rust Analytics, [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly matches these lists: 2x Rust servers and Modded Rust servers. These filters bring it up 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.

Joining the Server

What steps do I take to join [IND/SEA] RustNexus | Vanilla+ | 2x Gather | Biweekly?

Type client.connect 148.113.24.99:29029 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you. For more information, go to https://rust.nexnise.com/.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp40
Max players Capacity: 40 slots.
ts8
Group limit 8 per team: the default setting, unchanged.
v2634
Protocol Protocol 2634: matching game versions are required to join.
cs167781
Build Game build: 167781.
ptrak
Networking RakNet, the network layer the game ships with.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly Two-week wipe cycle.

Difficulty

^v
Vanilla No altered rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded The Modded listing applies: plugins or settings change play.

Region

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