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

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 9m ago · 139.99.124.11:28015

Abstract

We describe the public Rust server [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, reached at 139.99.124.11:28015 and hosted in EA. At the last check it held 4 of 200 places, against a seven-day mean of 4 and a peak of 15¹. It ranks #1,597 of all servers, the top 7%, and #158 in EA. It last wiped 9h ago on a published biweekly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsbiweekly wipes vanilla oxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	4/200	2% full
In the queue	0	no queue
Seven-day mean	4	peak 15, 48 h peak 5
Rank²	#1,597	top 7%; #158 in EA
Last wipe	9h ago	biweekly schedule
Next wipe³	7d 14h	Thu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeakWipe

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

Server fpsWipe

Figure 2: Server performance. 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.

4Rank

The server stands in the top 7% of all ranked servers, the top 28% in EA. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: from its schedule tag

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 14h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	14 days	between real wipes
On rhythm	67%	of its recent wipes
Wipe-day peak	31	players, last three wipes
Crowd held	33%	else halves by day 8.5

Table 3: Coming wipes, as expected.

When (UTC)	In	Kind
Thu 5 Nov, 19:00	7d 14h	force wipefw
Wed 11 Nov, 19:34	13d 14h	its own schedule
Wed 25 Nov, 19:34	27d 14h	its own schedule
Thu 3 Dec, 19:00	35d 14h	force wipefw
Wed 9 Dec, 19:34	41d 14h	its own schedule

Thu 15 OctThu 1 OctTue 15 Sep

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 34, 18 hours in.

5.2History

Table 4: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Wed 28 Oct, 19:349h ago	–	–	running	1
Thu 15 Oct, 17:4813d ago	34	halved by day 7	13.1 d	4
Thu 1 Oct, 18:03fw27d ago	28	held half	14 d	0
Tue 15 Sep, 15:4943d ago	32	halved by day 10	16.1 d	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla — Figure 5: The map: Procedural Map, size 3500, seed 1444129400. Open on RustMaps.

Table 5: The server's published settings.

Address	`139.99.124.11:28015`
Region	EA
Max players	200
Group limit	8, the default
Wipe schedule	biweekly
Last wipe	28 Oct 2026, 19:34 UTC
Hostname	–
First seen	13 Sep 2026
Map	Procedural Map
Size	3500
Seed	1444129400

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2], live vanilla server list [3] and next Rust wipe times [4].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 65 on average	13/200
Japan Tokyo - Mondays\|10/19\|JP/KR/SEA\|2週間\|JumpRust.comEA · groups of 8+ · biweekly · 41 on average	10/215
Rustafied.com - SEA MediumEA · groups of 16+ · biweekly · 27 on average	7/100
JP ONLY 2WEEK SOLO/DUO/TORIO#84EA · groups of 8+ · biweekly · 3 on average	1/60
[SEA] BRUNEI/MALAYSIA/INDONESIA \| Rust Battleground \| Biweekly EA · groups of 8+ · biweekly · 2 on average	1/100
新手村 \| Rookie Village \| 四人 \| 1x PVP 10.26新开EA · groups of 8+ · 1x · biweekly · 1 on average	2/500

Appendix AQuick answers

From the figures on this page.

About the server

A.1Does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla perform well?

Its average server fps over the last 48 hours was 126, with a minimum of 14. The highest number of entities it carried was 117,251, comprising buildings, deployables and all other objects. The peak memory usage was 4,282 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What location does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla have?

In Asia, according to its own listing, [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla appears with the EA tag. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 139.99.124.11:28015 is its address.

A.3What is the reliability of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, and is it online?

[SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla is online at this time. The uptime it reports indicates a restart about 4 hours ago. Its uptime over the last full days (7 days) was 99%, with 167 of 168 hours online. It was first observed on 13 September 2026 by Rust Statistics.

A.4What version of Rust is run on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

The version of Rust on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla is network protocol 2635 and build 168909, and the operating system is Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5What schedule does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla follow for wipes?

The record of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla's wipes is too sparse to confirm the schedule, so the prediction is based on its tag. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. 9 hours have passed since the current world was generated. Wipes every two weeks are published in the tags.

A.6How would you describe wipe day on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

Recent wipes saw an average peak of 31 players. The crowd reached its maximum 18 hours after the latest wipe. Half the peak was sustained until the next wipe in 33% of recent wipes. If not, the population dropped below half by day 8.5.

Player count

A.7What is the rank of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla among Rust servers?

On player hours over seven days [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla is #1,597, within the top 7% of all ranked servers; within Asia it is #158.

A.8What is the population level of [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

On [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla, 4 of the 200 slots are occupied at present. The peak over seven days is 15, against an average of 4. Of the last 48 hours, the peak hour falls at 15:00 UTC, with an average of 4 players.

Tags, lists

A.9What is the meaning of the tags on [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp200 (Max players): 200 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^b (Biweekly): Wipes take place once a fortnight; ^v (Vanilla): Rates, kits and rules are unchanged from the game Facepunch ships; ^o (Oxide): The plugin framework in use is Oxide (uMod); EA (East Asia): In the server browser it is filed under East Asia, which [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla be found among the Rust Statistics lists and filters?

Rust community servers, measured and Vanilla Rust servers are the Rust Statistics lists that [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla fits. You will find it on the server list filtered by: 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.

Rules, settings, map

A.11Under what rules and settings does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla operate?

Its name carries no gather rate for [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla. The group cap is 8 players, which is the default in the game. The mode is survival, which means gather, build and raid: the standard game. Fighting and raiding between players are both permitted. Community is its category in the server browser. Oxide plugins are running. By its own label, vanilla, rates, kits and rules are unchanged from the game Facepunch ships. The server has VAC on, Valve's anti-cheat.

A.12On which map does [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla take place?

The game generates [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla's procedural map at size 3,500, from seed 1444129400. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

Connection

A.13What is the process for joining [SEA/KR/JP] Rusty Malaysia | Biweekly | Vanilla?

Enter client.connect 139.99.124.11:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. Its website can be found at https://discord.com/invite/G4kV5sDrjr.

Appendix BServer tags

What each of the server's tags means. Published as mp200,ptrak,$r?,v2635,^b,^v,EA,gmrust,cs168909,ts8,^o.

Table 7: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp200`	Max players. 200 slots are available.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2635`	Protocol. Your game must run protocol 2635 to connect.
`cs168909`	Build. The game build is 168909.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. The region code is unset.
Wipe schedule
`^b`	Biweekly. Wipes take place once a fortnight.
Difficulty
`^v`	Vanilla. Rates, kits and rules are unchanged from the game Facepunch ships.
Mods and access
`^o`	Oxide. The plugin framework in use is Oxide (uMod).
Region
`EA`	East Asia. In the server browser it is filed 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.

Appendix CAbout this server, in its own words

NON PLAYING ADMIN ACTIVE Be Nice and Politely ! RULES Max team of 6 for Squads Server. Teaming, Cheating will be banned! (Teaming ban will be on admins discretion depending on the server impact of the team) Can be Perma-ban or timed ban. Using macros/scripts to lessen recoil will be considered cheating. Team of cheaters will be banned. Toxic voice/chat will be time-banned/muted. No to racism and discrimination. (Admins discretion to mute players involved depending on the severity of the offense) VAC/Game Bans within 100 days will automatically be banned from the servers. VAC/Game Bans that happened while playing on the server will automatically be PERMA-BANNED. Promoting other servers will be banned. Exposing personal information of other players will not be taken lightly and will likely cause you Timed-ban. (Names, Birthdays, Addresses, etc..) Exposing ADMIN's personal information will not be taken lightly and will likely cause you to be banned. This includes mentioning ADMIN's name in chat. Admins will rename players that have bad words names or something similar Accusations against ADMINS/MODS will not be taken lightly. Spreading of false information about the admins will be subject to time-ban or perma-ban depending on severity of the offense. You will first receive a warning and if you still continue to accuse the ADMINS/MODS, we will have you banned. Respect Admins Be nice and we will try our best to resolve the issue. Threats of any kind will not be taken lightly and will result in a permanent ban.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Live vanilla server list. ruststatistics.org/top-vanilla-rust-servers.
[4]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.