Rust Data

rustdata.spaceservers103.212.136.191:27017.ipynb

Run all rust-data · live

‹ All servers

Offline 103.212.136.191:28015 checked 27d ago

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

oxide

Connect

srv = rust.server("103.212.136.191:27017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 0 # peak –
rank #14,669 # top 64%
last wipe 27d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 64% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap0.3 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 12:00 UTC27d ago 1 NaN running 0
1 Fri 2 Oct, 05:43 UTC27d ago 1 NaN 0.3 days 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.

display(srv.map, srv.info())

Map

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
103.212.136.191:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 12:00 UTC
hostname
–
first seen
1 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average279/375
1Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average10/550
2Rustoria.co - SEA LongEA · groups of 12+ · monthly · 101 on average59/200
3Rustafied.com - SEA MainEA · groups of 16+ · weekly · 80 on average136/450
4Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 54 on average6/200
5[ASIA] Siam Rust | Vanilla | WeeklyEA · groups of 8+ · weekly · 38 on average77/180

Quick answers

From the figures on this page.

Player counts

How does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) compare in the rankings?

Player hours over seven days put [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) at #14,669, in the top 64% of the ranked set.

How many players does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) hold at once?

[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) returns no live count at this refresh, having last been seen 27 days 6 hours ago.

Server data

What Rust version does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) run?

The build is Rust network protocol 2634 and build 166586 on Linux, run by [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0). The protocol has to match before you can join, and Steam does the updating.

How reliable is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), and is it up?

Offline now for [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), last seen 27 days 6 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 1 October 2026.

In which location is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) hosted?

The name of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) points to Asia, even though no region tag is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 103.212.136.191:28015.

Map and rules

What rules and settings are recorded for [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

You will not find a gather rate in the string [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0). No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Wipe data

On what schedule does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) wipe?

The record for [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 27 days 7 hours ago, and that is the one in play.

On [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), what happens on wipe day?

The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) appear among Rust Data lists and filters?

These Rust Data lists include [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0): Rust community servers, unfiltered. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.

How should you read the server tags on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

Read by the game's server browser, the tags [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): Build number: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod). At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

Enter client.connect 103.212.136.191:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players Slot count: 100.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol The server speaks protocol 2634, so match your game version.
cs166586
Build Build number: 166586.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: 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.

Rust Data 104,335 players 11,883 servers online