Rust StatisticsWorking papers on every public Rust server · 49,675 players now

[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 27d ago · 103.212.136.191:28015

Abstract

We describe the public Rust server [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), reached at 103.212.136.191:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #14,669 of all servers, the top 64%. It last wiped 27d ago.

Keywordsoxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/1001% full
In the queue0no queue
Seven-day mean0peak –
Rank2#14,669top 64%
Last wipe27d agono schedule published
Next wipe3–too few wipes seen yet

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.

No hourly history yet.
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 memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
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.

4Rank

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

RankRank in region
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.3 daysbetween real wipes
Wipe-day peak1players, last three wipes
Fri 2 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 2 Oct, 12:0027d ago 1 – running 0
Fri 2 Oct, 05:4327d ago 1 – 0.3 d 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. 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

Custom map, no picture published
Figure 5: The map: Custom Map.
Table 4: The server's published settings.
Address103.212.136.191:28015
Region–
Max players100
Group limit8, the default
Wipe schedule–
Last wipe2 Oct 2026, 12:00 UTC
Hostname–
First seen1 Oct 2026
MapCustom Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust community servers listed [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - SEA MainEA · groups of 16+ · weekly · 180 on average93/200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average4/550
Rustoria.co - SEA LongEA · groups of 12+ · monthly · 100 on average14/200
Rustafied.com - SEA MainEA · groups of 16+ · weekly · 79 on average48/100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 54 on average2/200
[ASIA] Siam Rust | Vanilla | WeeklyEA · groups of 8+ · weekly · 37 on average31/150

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) have?

No region tag is published by [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), but its name points to Asia. Rust Statistics does not look up the machine's location; it shows where the server says it is. 103.212.136.191:28015 is its address.

A.2What is the reliability of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), and is it online?

[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is currently offline, with the last sighting 27 days 13 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. The first record of it by Rust Statistics dates to 1 October 2026.

A.3What is the Rust version for [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

The version of Rust on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is network protocol 2634 and build 166586, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4On what cycle does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) wipe?

The record of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)'s wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 27 days 14 hours.

A.5What happens on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) when wipe day arrives?

The average busiest point of recent wipes was 1 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6How does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) at #14,669, within the top 64% of ranked servers.

A.7At what level does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) operate in terms of players?

The last recorded sighting of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) was 27 days 13 hours ago; it is offline now.

Tags, lists

A.8What do the tags associated with [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) signify?

The game's server browser reads gmrust (Game mode): This is survival as standard Rust plays; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166586 (Build): Build 166586 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod), which [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) publishes as its tags. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) fits. You will find it on the server list filtered by: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.

Settings and map

A.10Which settings and rules are in force on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

The name of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) states no gather rate. At 8 players, the group limit equals the game's default. survival is the game mode here; gather, build and raid: the standard game. Fighting and raiding between players are both permitted. The server browser lists it under Community. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.

Connection

A.11How do you connect to [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

Press F1 inside Rust to open the console and enter client.connect 103.212.136.191:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp100,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp100Max players. 100 slots are available.
ts8Group limit. 8 per team, the value the game sets by default.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs166586Build. Build 166586 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.