Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO V SRV11,720online PAX60,549playing OCC3,378with players WIPED 3H181
VANVanilla traffic
Callsign

SEA1590↑

[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla

Online EA 139.99.124.11:28015 checked 10m ago

biweekly wipes vanillaoxide
Clearance · join
Players now 14/ 200 7% full
7-day average4peak 15
Rank#1,590top 7% · #157 in EA
Last wipe15h agobiweekly schedule
Next wipe7d 7hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeakWipe
0510152012:0021:0006:0014:0000:0009:00Wiped Wed 28 Oct, 19:34 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
05010015020012:0021:0006:0014:0000:0009:00Wiped Wed 28 Oct, 19:34 UTCWIPE

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
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 7% of all ranked servers, top 28% 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 5 November, 19:00 UTC, in 7d 7h.

The force wipe · high confidence

usual gap14 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak31players, last three wipes
crowd held33%else halves by day 8.5

Coming wipes

  1. 7d 7hThu 5 Nov, 19:00 UTCFW
  2. 13d 8hWed 11 Nov, 19:34 UTC
  3. 27d 8hWed 25 Nov, 19:34 UTC
  4. 35d 7hThu 3 Dec, 19:00 UTCFW
  5. 41d 8hWed 9 Dec, 19:34 UTC

The first 48 hours of its last wipes

Thu 15 OctThu 1 OctTue 15 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 34, 18 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 19:34 UTC15h ago – – running 1
Thu 15 Oct, 17:48 UTC13d ago 34 halved by day 7 13.1 days 4
Thu 1 Oct, 18:03 UTC FW27d ago 28 held half 14 days 0
Tue 15 Sep, 15:49 UTC43d ago 32 halved by day 10 16.1 days 8

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. 01COM
    Callsign RST015EA · groups of 16+ · biweekly · 66 on average Rustoria.co - SEA Medium
    Players 361/375
  2. 02COM
    Callsign JPN778EA · groups of 8+ · biweekly · 39 on average Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com
    Players 24/215
  3. 03COM
    Callsign RST018EA · groups of 16+ · biweekly · 26 on average Rustafied.com - SEA Medium
    Players 67/250
  4. 04COM
    Callsign ONL015EA · groups of 8+ · biweekly · 3 on average JP ONLY 2WEEK SOLO/DUO/TORIO#84
    Players 2/60
  5. 05COM
    Callsign SEA428EA · groups of 8+ · biweekly · 2 on average [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly
    Players 2/100
  6. 06COM
    Callsign RKO016EA · groups of 8+ · 1x · biweekly · 1 on average 新手村 | Rookie Village | 四人 | 1x PVP 10.26新开
    Players 0/500
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

These Rust Tracker lists carry [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla: Community servers, no tags and Vanilla Rust servers, tracked live. These filters surface it on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours; Players now: At least 10.

What do the tags mean that [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla is listed under?

The game's server browser reads these tags from [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla: gmrust (Game mode): Survival as standard Rust plays; mp200 (Max players): Capacity: 200 slots; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): Facepunch's game unaltered: rates, kits and rules unchanged; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): Server browser: listed under East Asia. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.

Wipe Times

What should you expect on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla when wipe day lands?

The average peak across recent wipes: 31 players. The peak on the latest wipe came 18 hours after it. Half the peak was held until the next wipe in 33% of its recent wipes. By day 8.5 the crowd dropped below half where it did not hold.

When does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla wipe?

The prediction for [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla follows its tag, as too few wipes are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its world went live 15 hours. Its tags carry an every-two-weeks wipe schedule.

Location and Status

Is [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla up, and how does its uptime hold?

Tracking shows [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla online as of now. By its own uptime figure, the last restart was roughly 10 hours ago. 99% uptime over the last 7 full days, with 167 of 168 hours up. Rust Tracker logged it first on 13 September 2026.

Which Rust version is confirmed on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

Rust network protocol 2635 and build 168909 on Linux is what [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla runs. The same protocol is required to join, and Steam updates it for you.

What is performance like on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

Average server fps over the last 48 hours: 128, with a low of 14. Buildings, deployables and the rest of the world took it to a maximum of 117,014 entities. Peak memory use: 4,282 MB. A climbing entity count and low fps are what register as lag for players.

Which location is [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla in?

Listed in Asia under EA: that is [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla by its own tags. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 139.99.124.11:28015.

Population

How many players are on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla right now?

Slots 200; players on board 14: that is [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla now. Seven-day average 4 players; peak 15. Peak traffic in the last 48 hours came at 07:00 UTC, averaging 14 players.

How does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla compare in the rankings?

Top 7% of all ranked servers and #157 in Asia: [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla ranks #1,590 on player hours over the last seven days.

Settings

Which settings and rules are confirmed on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

Nothing in [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla's name states a gather rate. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build, raid, as the game intends. Fighting and raiding between players are on. Listed under Community in the server browser, it is a community server. Plugins on it: Oxide. Its label is vanilla: facepunch's game unaltered: rates, kits and rules unchanged. On: VAC, Valve's anti-cheat.

What map is [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla on?

A procedural map of size 3,500 runs on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, generated by the game from seed 1444129400. Look at it on RustMaps from this page: equal size and seed return the same map.

Connect

How do you get onto [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

To connect: start Rust, press F1, enter client.connect 139.99.124.11:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://discord.com/invite/G4kV5sDrjr.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp200
Max players Capacity: 200 slots.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla Facepunch's game unaltered: rates, kits and rules unchanged.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

Region

EA
East Asia Server browser: listed 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.