Working its way up from the back of the class: #12,720 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
5/ 100
F
Lost ground: down 11,526 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (D); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
Top 53% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The name of [SEA/IND] Badnaam 2.0 points to Asia, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 103.212.136.191:28015 is the address to use.
How reliable is [SEA/IND] Badnaam 2.0, and is it up?
You cannot join now: [SEA/IND] Badnaam 2.0 is offline, last seen 28 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 25 September 2026, Rust Server Score saw it for the first time.
Which Rust version is [SEA/IND] Badnaam 2.0 running?
Rust network protocol 2633 and build 165217 on Linux is what [SEA/IND] Badnaam 2.0 runs. To join, your game must use the same protocol; Steam handles the update.
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 tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 32 days 4 hours.
Population
Where does [SEA/IND] Badnaam 2.0 sit among Rust servers?
In the top 53% of all ranked servers, [SEA/IND] Badnaam 2.0 sits at #12,720 for player hours over the last seven days.
Is [SEA/IND] Badnaam 2.0 a busy server?
[SEA/IND] Badnaam 2.0 is offline at the moment; the last time it was seen was 28 days 16 hours ago.
Tags and filters
What is meant by the tags on [SEA/IND] Badnaam 2.0?
You'll see [SEA/IND] Badnaam 2.0 tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show [SEA/IND] Badnaam 2.0?
Rust Server Score lists that include [SEA/IND] Badnaam 2.0: Best community servers, graded. These filters bring it up 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.
Server rules
What settings and rules apply on [SEA/IND] Badnaam 2.0?
The name of [SEA/IND] Badnaam 2.0 gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
How to join
What is the way to join [SEA/IND] Badnaam 2.0?
Enter client.connect 103.212.136.191:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework 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.
A term to build on. Strongest in standing (D); momentum is the one to work on (F).