RUST METRICSFlight deck · live data
Data live Servers11,698 Players53,885 Populated3,236 Fresh wipes 3 h139 Scan5 min
‹ All servers139.99.124.11:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online EA 139.99.124.11:28015 checked 12m ago

biweekly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Thu 08:00 UTC
0 50 100 150 200 PAX 10 /200

Players now

5% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 134 SERVER FPS

Server fps

48 h low 14 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 72,075 ×1000

Entities

48 h range 53,011–117,014 · memory 2,293 MB
1239 ET SINCE RESTART 09:00

Uptime

9 h 0 min since its last restart, at the last reading
7-day average4peak 15
Rank#1,585top 7% · #157 in EA
Last wipe14h agobiweekly schedule
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
Memory2,293MB48 h peak 14 players
REC 1

Players

AveragePeakWipe
0510152011:0020:0005:0013:0023:0008:00Wiped Wed 28 Oct, 19:34 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020011:0020:0005:0013:0023:0008: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.

REC 3

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.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. 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. WPT 1Thu 5 Nov, 19:00 UTC7d 8hFW
  2. WPT 2Wed 11 Nov, 19:34 UTC13d 9h
  3. WPT 3Wed 25 Nov, 19:34 UTC27d 9h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 8hFW
  5. WPT 5Wed 9 Dec, 19:34 UTC41d 9h

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.

LOG

Wipes

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

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla when wipe day comes?

At their busiest, its recent wipes drew 31 players on average. 18 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 33% of recent wipes. It fell below half by day 8.5 when it didn't.

What wipe timing does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla follow?

The prediction follows its tag, because too few of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla's wipes are on record to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 14 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.

Lists and filters

How should you read the tags on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp200 (Max players): Slots: 200; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): It wipes once a fortnight; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; EA (East Asia): East Asia is the browser category it sits in from [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla appear in Rust Metrics lists and filters?

These Rust Metrics lists carry [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla: Rust community servers: live readings and Vanilla Rust servers, live. These filters bring it up 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.

Player count

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

Top 7% of all ranked servers: [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla takes #1,585 on seven-day player hours and #157 in Asia.

What player count does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla carry?

Current headcount on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla: 10 players, 200 slots available. Seven-day check: 4 players on average. Peak reading: 15. The last 48 hours peaked at 07:00 UTC, averaging 14 players at that hour.

Server

Which location does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla run from?

Reading: location. The EA tag puts [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 139.99.124.11:28015.

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

Reading: [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla within range?

Check: fps. Average 128 server fps over the last 48 hours, low of 14. Within range. Peak entity count: 117,014. Buildings, deployables and all else included. Reading: 4,282 MB of memory at the highest. Expect lag when fps falls and entities climb.

What is the uptime on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, and is it online?

Check: connection. [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla is online at this moment. Check: restart. The uptime it reports puts the last restart about 9 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

How is [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla configured, and what rules are in force?

Check: gather rate. The name [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Plugin count: Oxide. Vanilla is the label it uses: rates, kits and rules are exactly as Facepunch ships them. Anti-cheat reading: VAC on, Valve's system.

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

Size 3,500 and seed 1444129400: the game generates the procedural map on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How do you connect to [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

To join: start Rust, press F1 and type client.connect 139.99.124.11:28015. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/G4kV5sDrjr is where its website sits.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp200
Max players Slots: 200.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly It wipes once a fortnight.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

Region

EA
East Asia East Asia is the browser category it sits in.

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.