Rust Data LabData lab · live
Live readings Servers11,613 Players33,251 Populated2,788 Fresh wipes · 3h71 Sampled every 5 min

Element card · group Vanilla · atomic number 1,598, its rank

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

Online EA 139.99.124.11:28015 checked 9m ago

biweekly wipes vanillaoxide
Join the experiment
Atomic mass · players now 8/ 200 4% full Room to join
7-day average4peak 15
Rank · atomic number#1,598top 7% · #158 in EA
Last wipe10h agobiweekly schedule
Next wipe7d 12hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeakWipe
0246807:0016:0001:0010:0020:0005:00Wiped Wed 28 Oct, 19:34 UTCWIPE

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
Server fpsWipe
05010015020007:0016:0001:0010:0020:0005: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.

Result 03

Rank

Result

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.

Reaction kinetics

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. 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 12hThu 5 Nov, 19:00 UTCFW
  2. 13d 13hWed 11 Nov, 19:34 UTC
  3. 27d 13hWed 25 Nov, 19:34 UTC
  4. 35d 12hThu 3 Dec, 19:00 UTCFW
  5. 41d 13hWed 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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 19:34 UTC10h 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rustoria.co - … 24
    Rustoria.co - SEA Medium EA · groups of 16+ · biweekly · 64 on average 24/ 200
  2. 2 Ja Japan Tokyo - … 13
    Japan Tokyo - Mondays|10/19|JP/KR/SEA|2週間|JumpRust.com EA · groups of 8+ · biweekly · 41 on average 13/ 215
  3. 3 Ru Rustafied.com … 11
    Rustafied.com - SEA Medium EA · groups of 16+ · biweekly · 27 on average 11/ 100
  4. 4 Jp JP ONLY 2WEEK … 0
    JP ONLY 2WEEK SOLO/DUO/TORIO#84 EA · groups of 8+ · biweekly · 3 on average 0/ 60
  5. 5 Br [SEA] BRUNEI/M… 1
    [SEA] BRUNEI/MALAYSIA/INDONESIA | Rust Battleground | Biweekly EA · groups of 8+ · biweekly · 2 on average 1/ 100
  6. 6 新手 新手村 | Rookie V… 2
    新手村 | Rookie Village | 四人 | 1x PVP 10.26新开 EA · groups of 8+ · 1x · biweekly · 1 on average 2/ 500

Quick answers

from the figures on this page

Server setup

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

A procedural map of size 3,500 with seed 1444129400 runs on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, generated by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page.

What rules has [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla set, and what settings are in force?

The name of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla carries no gather rate. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. It appears under Community in the server browser. Oxide plugins are running on it. Vanilla is its own label: nothing is changed: rates, kits and rules are as Facepunch ships them. The VAC anti-cheat from Valve is enabled.

Server details

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

[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla gives Asia as its location, using the EA tag. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 139.99.124.11:28015.

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

Rust network protocol 2635 and build 168909 on Linux is what [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla uses. The protocol must match for you to join; Steam will update your game.

Does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla stay up, and how reliable is its uptime?

Right now, [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla is reachable. According to the uptime it reports, the last restart was about 6 hours ago. For the last 7 full days, 167 of 168 hours were online, giving 99% uptime. The first sighting by Rust Data Lab was on 13 September 2026.

How well does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla perform?

In the last 48 hours, it averaged 127 server fps, with a low of 14. The maximum entity count was 117,014, covering buildings, deployables and all else in the world. The highest memory usage was 4,282 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipes and resets

When does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla wipe, and how often?

Following the tag is the best the prediction can do for [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, whose record holds too few wipes to confirm its schedule. The next time this server wipes will be the force wipe on Thursday 5 November at 19:00 UTC, which wipes every Rust server. 10 hours ago the current world was made. Wipes every two weeks are what its tags set out.

How does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla look on the day of a wipe?

Recent wipes on average reached 31 players at their busiest. The latest wipe's peak fell 18 hours after it began. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. Where it did not hold, the crowd dropped below half by day 8.5.

Tags, lists

Which meanings sit behind the tags on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

The game's server browser reads the tags [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla publishes, which are gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): Player slots: 200; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^b (Biweekly): The map wipes on a two-week cycle; ^v (Vanilla): Nothing is changed: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugins run through Oxide (uMod); EA (East Asia): The server browser files it under East Asia. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla come up?

These themed Rust Data Lab lists carry [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla: Rust community servers, measured and Vanilla Rust servers, measured. Applying these filters on the server list returns it: 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.

Population

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

Player hours for the past seven days give [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla #1,598, #158 in Asia, and a place in the top 7% of ranked servers.

What does the current player count on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla tell you?

At the moment [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla has 8 of its 200 slots filled. The week's figures average 4 players and top out at 15. Over 48 hours, the highest average fell at 05:00 UTC, at 5 players.

Connection

What is the way to join [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

In Rust, press F1 and enter client.connect 139.99.124.11:28015. Or click Launch Rust here to open Rust via Steam and connect automatically. You can find its website at https://discord.com/invite/G4kV5sDrjr.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp200
Max players Player slots: 200.
ts8
Group limit This uses the game's default: 8 per team.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The map wipes on a two-week cycle.

Difficulty

^v
Vanilla Nothing is changed: rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).

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.