Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h18 48 h

Station XX-15497 · no signal

[SEA/IND] Badnaam 2.0

Offline 103.212.136.180:28015 checked 35d ago

oxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,497
top 67%
Last wipe
40d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15497 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 100 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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.

Channel 3 · rank movement

Rank

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.

Expected events

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 peak
50players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 18 Sep, 12:50 UTC40d ago M1.7rising 50 – running 2

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

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

Quick answers

from the figures on this page

Map and rules

Which map is running on [SEA/IND] Badnaam 2.0?

Generated by the game, the map on [SEA/IND] Badnaam 2.0 is procedural, size 3,750 with seed 1337. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on [SEA/IND] Badnaam 2.0?

You will find no gather rate in the name of [SEA/IND] Badnaam 2.0. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. It is a community server, and the browser lists it under Community. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on [SEA/IND] Badnaam 2.0?

A reading taken now finds [SEA/IND] Badnaam 2.0 offline; the most recent activity was 35 days 15 hours ago.

How does [SEA/IND] Badnaam 2.0 rank against other Rust servers?

On player hours for the past week, [SEA/IND] Badnaam 2.0 sits at #15,497, which puts it inside the top 67% of every ranked server.

Server facts

How reliably does [SEA/IND] Badnaam 2.0 stay online?

As recorded now, [SEA/IND] Badnaam 2.0 is not reachable, the last contact having been 35 days 15 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.

Which region does [SEA/IND] Badnaam 2.0 run from?

Its name points to Asia, but [SEA/IND] Badnaam 2.0 publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 103.212.136.180:28015.

What build of Rust does [SEA/IND] Badnaam 2.0 use?

On Linux, [SEA/IND] Badnaam 2.0 runs Rust network protocol 2633 and build 164530. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on [SEA/IND] Badnaam 2.0?

The recent wipes averaged a busiest count of 50 players. 5 hours after the latest wipe, the crowd peaked.

On what timetable does [SEA/IND] Badnaam 2.0 run its wipes?

Too few wipes of [SEA/IND] Badnaam 2.0 are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 40 days 6 hours is how long the current world has been running.

Tags

What do the server tags on [SEA/IND] Badnaam 2.0 mean?

The game's server browser reads the tags [SEA/IND] Badnaam 2.0 publishes: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs164530 (Build): Game build: 164530; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [SEA/IND] Badnaam 2.0 appear?

The Rust Server Trends lists that take in [SEA/IND] Badnaam 2.0 are: Rust community servers without the side modes. You will find it under these filters 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.

Connecting

How do you connect to [SEA/IND] Badnaam 2.0?

Enter client.connect 103.212.136.180:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. https://chernobyl.in/ is where its website lives.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs164530
Build Game build: 164530.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.