Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO M SRV11,850online PAX85,370playing OCC3,783with players WIPED 3H296
COMCommunity traffic
Callsign

SEA12720

[SEA/IND] Badnaam 2.0

Offline 103.212.136.191:28015 checked 30d ago

oxide
Clearance · join
Players now 2/ 100 2% full
7-day average0peak –
Rank#12,720top 53%
Last wipe34d agono schedule published
Next wipe–no wipe seen yet
Track history

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

Flight plan

Wipe schedule

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

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01COM
    Callsign RST015EA · groups of 16+ · weekly · 181 on average Rustoria.co - SEA Main
    Players 442/450
  2. 02COM
    Callsign JPN002EA · groups of 16+ · weekly · 119 on average Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com
    Players 30/550
  3. 03COM
    Callsign RST015EA · groups of 12+ · monthly · 103 on average Rustoria.co - SEA Long
    Players 74/200
  4. 04COM
    Callsign RST018EA · groups of 16+ · weekly · 82 on average Rustafied.com - SEA Main
    Players 259/450
  5. 05COM
    Callsign RST018EA · no group limit · 65 on average Rustoria.co - SEA Medium | JUST WIPED 29.10
    Players 57/100
  6. 06COM
    Callsign JPN016EA · groups of 8+ · weekly · 53 on average Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]
    Players 22/200
ATIS · this server

Quick answers

From the figures on this page.

Filters

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

On Rust Tracker, [SEA/IND] Badnaam 2.0 sits in these lists: Community servers, no tags. It comes up 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 should you read the tags on [SEA/IND] Badnaam 2.0?

These tags are published by [SEA/IND] Badnaam 2.0 for the game's server browser to read: gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Join only if your game is on protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework confirmed: Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Schedule

Which wipe times are confirmed for [SEA/IND] Badnaam 2.0?

The record holds too few of [SEA/IND] Badnaam 2.0's wipes to show its rhythm. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. Its world went live 34 days 2 hours.

Server Details

What is the uptime on [SEA/IND] Badnaam 2.0, and is it online?

Offline now, [SEA/IND] Badnaam 2.0 was last seen 30 days 14 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 25 September 2026.

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

Rust network protocol 2633 and build 165217 on Linux is what [SEA/IND] Badnaam 2.0 runs. Steam updates it for you; your game must share the protocol to join.

Where does [SEA/IND] Badnaam 2.0 sit?

No region tag from [SEA/IND] Badnaam 2.0, but the name points to Asia. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 103.212.136.191:28015.

Player Count

What is the player count on [SEA/IND] Badnaam 2.0?

Last seen 30 days 14 hours ago; [SEA/IND] Badnaam 2.0 is offline at present.

How does [SEA/IND] Badnaam 2.0 compare in the rankings?

On player hours over seven days, [SEA/IND] Badnaam 2.0 ranks #12,720, inside the top 53% of all ranked servers.

Settings

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

Nothing in [SEA/IND] Badnaam 2.0's name states a gather rate. 8 players per group is the game's default, and the cap holds. survival is the game mode, gather, build, raid, as the game intends. Players can raid and fight each other here. The server browser lists it under Community, as a community server. Plugins on it: Oxide. VAC is on, Valve's anti-cheat.

Connect

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

To connect: start Rust, press F1, enter client.connect 103.212.136.191:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

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.
mp100
Max players 100 slots on this server.
ts8
Group limit Default team size: 8.
v2633
Protocol Join only if your game is on protocol 2633.
cs165217
Build The game build is 165217.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code No region code is set.

Mods and access

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