Offline 103.212.136.180:28015 checked 35d ago

[SEA/IND] Badnaam 2.0

oxide

Connect

srv = rust.server("103.212.136.180:28016")
print(srv.connect_command)

Launch Rust and join Website

Right now

srv.summary()

players now 0/100 # 0% full

7-day average 0 # peak –

rank #15,497 # top 67%

last wipe 40d ago # no schedule published

next wipe – # too few wipes seen yet

display(Image(srv.banner))

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, measured since 17 Sep. 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

Top 67% 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.

wipe-day peak50players, last three wipes

The first 48 hours of its last wipes

Players each hour, from the hour of the wipe. The latest peaked at 50, 5 hours in.

Wipes · newest first

srv.wipes.head(20)

	wiped	peak	crowd	lasted	players_before
	datetime64[UTC]	int64	object	timedelta	int64
0	Fri 18 Sep, 12:50 UTC40d ago	50	NaN	running	2

# 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

3750 · seed 1337

map: Custom Map
size: 3750
seed: 1337

Server

srv.info()

<class 'rust.Server'>
Index: 8 entries, address to first_seen

address: 103.212.136.180:28015
region: –
max players: 100
group limit: 8, the default
wipe schedule: –
last wipe: 18 Sep 2026, 12:50 UTC
hostname: –
first seen: 13 Sep 2026

About this server · in its own words

print(srv.description)

Welcome to Badnaam. The most toxic wasteland in the IND/SEA region. This is pure, unadulterated Vanilla Rust. No kits, no mods, no VIP passes, and absolutely no mercy. • 100% Pure Vanilla Experience • Map Size: 4250 • Wipe Schedule: Monthly Force Wipes & Weekly Map Wipes • Group Limits: None • Active, Non-Playing Admins Join the meltdown on Discord: https://discord.gg/Y4GDUtVYtE

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

rust.similar(srv).head(6)

	server	like_this	players
0	Rustoria.co - SEA Main	EA · groups of 16+ · weekly · 184 on average	9/200
1	Japan Tokyo - Main\|10/23\|JP/KR/SEA\|金曜日\|JumpRust.com	EA · groups of 16+ · weekly · 119 on average	13/550
2	Rustoria.co - SEA Long	EA · groups of 12+ · monthly · 107 on average	47/200
3	Rustafied.com - SEA Main	EA · groups of 16+ · weekly · 88 on average	4/100
4	Rustoria.co - SEA Medium \| JUST WIPED 28.10	EA · no group limit · 65 on average	68/100
5	Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA\|初心者]	EA · groups of 8+ · weekly · 52 on average	2/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does [SEA/IND] Badnaam 2.0 rank?

Rank #15,497 on seven-day player hours for [SEA/IND] Badnaam 2.0, within the top 67% of all ranked servers.

What population does [SEA/IND] Badnaam 2.0 carry?

[SEA/IND] Badnaam 2.0 returns no live count at this refresh, having last been seen 35 days 19 hours ago.

About the server

What is the Rust version on [SEA/IND] Badnaam 2.0?

Rust network protocol 2633 and build 164530 on Linux is what [SEA/IND] Badnaam 2.0 runs. Joining needs the same protocol on your game; Steam handles the update.

Is [SEA/IND] Badnaam 2.0 up, and what does its uptime show?

The latest sample has [SEA/IND] Badnaam 2.0 offline, with a last sighting 35 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.

In which location is [SEA/IND] Badnaam 2.0 hosted?

No region tag is published by [SEA/IND] Badnaam 2.0, though its name points to Asia. 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.180:28015.

Rules, settings, map

What rules and settings are recorded for [SEA/IND] Badnaam 2.0?

You will not find a gather rate in the string [SEA/IND] Badnaam 2.0. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. The server browser lists it under Community. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has [SEA/IND] Badnaam 2.0 loaded?

The game generates the map on [SEA/IND] Badnaam 2.0: procedural, size 3,750, seed 1337. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.

Wipe data

When does [SEA/IND] Badnaam 2.0 wipe, and how often?

A rhythm cannot be read from the wipes of [SEA/IND] Badnaam 2.0 on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 40 days 10 hours ago.

On [SEA/IND] Badnaam 2.0, what happens on wipe day?

Across recent wipes the busiest point averaged 50 players. 5 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Where does [SEA/IND] Badnaam 2.0 appear among Rust Data lists and filters?

The Rust Data lists that [SEA/IND] Badnaam 2.0 fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: 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] Badnaam 2.0?

Read by the game's server browser, the tags [SEA/IND] Badnaam 2.0 publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into [SEA/IND] Badnaam 2.0?

Enter client.connect 103.212.136.180:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://chernobyl.in/.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o

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.