Rust Data LabData lab · live
Live readings Servers11,829 Players89,289 Populated4,008 Fresh wipes · 3h0 Sampled every 5 min

Element card · group Community · atomic number 15,497, its rank

[SEA/IND] Badnaam 2.0

Offline 103.212.136.180:28015 checked 35d ago

oxide
Join the experiment
Atomic mass · players now 0/ 100 0% full Room to join
7-day average0peak –
Rank · atomic number#15,497top 67%
Last wipe40d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

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

Reaction kinetics

Wipe schedule

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.

wipe-day peak50players, last three wipes

The first 48 hours of its last wipes

020406080+0h+9h+19h+28h+38h+47h

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 18 Sep, 12:50 UTC40d ago 50 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rustoria.co - … 40
    Rustoria.co - SEA Main EA · groups of 16+ · weekly · 183 on average 40/ 200
  2. 2 Ja Japan Tokyo - … 29
    Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average 29/ 550
  3. 3 Ru Rustoria.co - … 103
    Rustoria.co - SEA Long EA · groups of 12+ · monthly · 107 on average 103/ 200
  4. 4 Ru Rustafied.com … 18
    Rustafied.com - SEA Main EA · groups of 16+ · weekly · 88 on average 18/ 100
  5. 5 Ru Rustoria.co - … 72
    Rustoria.co - SEA Medium | JUST WIPED 28.10 EA · no group limit · 65 on average 72/ 100
  6. 6 Ja Japan Beginner… 15
    Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 52 on average 15/ 200

Quick answers

from the figures on this page

Settings and map

What map is in play on [SEA/IND] Badnaam 2.0?

The map on [SEA/IND] Badnaam 2.0 is procedural at size 3,750 with seed 1337, made by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps. On the map name: Custom Map.

How is [SEA/IND] Badnaam 2.0 configured, and what rules apply?

Nothing in the name of [SEA/IND] Badnaam 2.0 gives a gather rate. Groups top out at 8 players, the default for the game. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. You will find it under Community in the server browser. Oxide plugins are running on it. VAC is on, Valve's anti-cheat.

Server facts

What region hosts [SEA/IND] Badnaam 2.0?

The name of [SEA/IND] Badnaam 2.0 points to Asia, even without a region tag. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. Connect at 103.212.136.180:28015.

What Rust version does [SEA/IND] Badnaam 2.0 currently run?

On Linux, [SEA/IND] Badnaam 2.0 is running Rust network protocol 2633 and build 164530. Joining requires the same protocol on your game; Steam takes care of updating it.

Does [SEA/IND] Badnaam 2.0 stay up, and how reliable is its uptime?

Right now [SEA/IND] Badnaam 2.0 is offline, with its last appearance 35 days 16 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. On 13 September 2026, Rust Data Lab saw it for the first time.

Wipe schedule

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

The record holds too few of [SEA/IND] Badnaam 2.0's wipes to show its rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 40 days 7 hours ago.

How does [SEA/IND] Badnaam 2.0 look on the day of a wipe?

Averaged across its recent wipes, the busiest point drew 50 players. The latest wipe's peak fell 5 hours after it began.

Where it appears

What should you understand from the tags [SEA/IND] Badnaam 2.0 carries?

gmrust (Game mode): Standard Rust survival is the game here; mp100 (Max players): It has 100 slots; ts8 (Group limit): This uses the game's default: 8 per team; v2633 (Protocol): Protocol 2633 is required; join only if your game matches it; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins: that is the tag list [SEA/IND] Badnaam 2.0 publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does [SEA/IND] Badnaam 2.0 come up?

The Rust Data Lab lists that include [SEA/IND] Badnaam 2.0 are: Rust community servers, measured. You can find it on the server list by applying these filters: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.

Player counts

What position does [SEA/IND] Badnaam 2.0 hold among Rust servers?

Player hours over the last week put [SEA/IND] Badnaam 2.0 at #15,497, inside the top 67% of ranked servers.

What does the current player count on [SEA/IND] Badnaam 2.0 tell you?

[SEA/IND] Badnaam 2.0 is offline at the moment; the last sighting was 35 days 16 hours ago.

Getting on

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

Open the console with F1 in Rust and type client.connect 103.212.136.180:28015. The Launch Rust button on this page does the same job through Steam. You can find its website at https://chernobyl.in/.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp100
Max players It has 100 slots.
ts8
Group limit This uses the game's default: 8 per team.
v2633
Protocol Protocol 2633 is required; join only if your game matches it.
cs164530
Build Build number: 164530.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.

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.