Rust Server TrendsSeismic network · station log
Recording Stations11,620 Players35,442 Active2,860 Wipes · 3 h74 48 h

Station XX-12720 · no signal

[SEA/IND] Badnaam 2.0

Offline 103.212.136.191:28015 checked 30d ago

oxide
Connect
Players now
2/ 100
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,720
top 53%
Last wipe
33d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-12720 · 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
2of 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. 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
15k10k15k20k25 Sep27 Sep29 Sep1 Oct3 Oct5 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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 · 183 on average
65/ 200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average
9/ 550
Rustoria.co - SEA Long EA · groups of 12+ · monthly · 106 on average
74/ 200
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 88 on average
17/ 100
Rustoria.co - SEA Medium | JUST WIPED 29.10 EA · no group limit · 65 on average
58/ 100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 53 on average
6/ 200
Readings, in words

Quick answers

from the figures on this page

Map and rules

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

No gather rate appears in the name of [SEA/IND] Badnaam 2.0. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Community, as a community server. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Population

How many players are recorded on [SEA/IND] Badnaam 2.0 right now?

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

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

The last seven days of player hours place [SEA/IND] Badnaam 2.0 at #12,720, in the top 53% of all ranked servers.

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 30 days 5 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 25 September 2026 is when Rust Server Trends first recorded it.

Where in the world is [SEA/IND] Badnaam 2.0 hosted?

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. You reach it at 103.212.136.191: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 165217. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

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

On record so far are too few of [SEA/IND] Badnaam 2.0's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 33 days 17 hours.

Tags

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

These are the tags [SEA/IND] Badnaam 2.0 publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; 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; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

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

These Rust Server Trends lists include [SEA/IND] Badnaam 2.0: 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.

How to join

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

Enter client.connect 103.212.136.191:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players 100 slots are available.
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.
cs165217
Build The game build is 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs 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.