RUST METRICSFlight deck · live data
Data live Servers11,873 Players96,161 Populated3,898 Fresh wipes 3 h387 Scan5 min
‹ All servers103.212.136.191:28015
Offline Full Queue Fresh wipe Wipe due No query

[SEA/IND] Badnaam 2.0

Offline 103.212.136.191:28015 checked 30d ago

oxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 2 /100

Players now

2% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#12,720top 53%
Last wipe34d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

When does [SEA/IND] Badnaam 2.0 wipe?

The rhythm of [SEA/IND] Badnaam 2.0's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 34 days 3 hours ago the current world was made.

Lists and filters

How should you read the tags on [SEA/IND] Badnaam 2.0?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod) from [SEA/IND] Badnaam 2.0. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [SEA/IND] Badnaam 2.0 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring [SEA/IND] Badnaam 2.0: Rust community servers: live readings. Reading: server list filters. It comes up under Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.

Occupancy

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

Ranking for [SEA/IND] Badnaam 2.0: #12,720 on seven-day player hours, top 53% of all ranked servers.

How full does [SEA/IND] Badnaam 2.0 get?

[SEA/IND] Badnaam 2.0 is not responding; status offline, last seen 30 days 15 hours ago.

Server details

What location is [SEA/IND] Badnaam 2.0 hosted in?

The name of [SEA/IND] Badnaam 2.0 points to Asia, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 103.212.136.191:28015.

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

Reading: [SEA/IND] Badnaam 2.0, Rust network protocol 2633 and build 165217, Linux. Check: protocol. To join, your game must match; Steam handles the update.

Is [SEA/IND] Badnaam 2.0 up, and how often does it stay up?

[SEA/IND] Badnaam 2.0 reports offline. The last reading came 30 days 15 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Map and rules

What rules does [SEA/IND] Badnaam 2.0 enforce, and what are its settings?

No gather rate appears in the name: [SEA/IND] Badnaam 2.0. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Connection

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

Press F1 in Rust and enter client.connect 103.212.136.191:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

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