Working its way up from the back of the class: #15,497 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
3/ 100
F
Lost ground: down 14,590 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 peak50players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 50, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 18 Sep, 12:50 UTC40d ago
50
–
running
2
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
No region tag appears for [SEA/IND] Badnaam 2.0, but the name suggests Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 103.212.136.180:28015 is the address to use.
Is [SEA/IND] Badnaam 2.0 up, and how steady is its uptime?
You cannot join now: [SEA/IND] Badnaam 2.0 is offline, last seen 35 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is [SEA/IND] Badnaam 2.0 running?
The server [SEA/IND] Badnaam 2.0 is on Rust network protocol 2633 and build 164530 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
When does [SEA/IND] Badnaam 2.0 wipe, and how often?
[SEA/IND] Badnaam 2.0 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 40 days 7 hours have passed since this world was made.
What happens on [SEA/IND] Badnaam 2.0 when wipe day arrives?
The average peak on its recent wipes was 50 players. 5 hours after the latest wipe began, the crowd hit its peak.
Player count
What position does [SEA/IND] Badnaam 2.0 hold in the rankings?
Over the last seven days, [SEA/IND] Badnaam 2.0 has #15,497 for player hours, in the top 67% of all ranked servers.
How many players does [SEA/IND] Badnaam 2.0 usually have?
The last sighting of [SEA/IND] Badnaam 2.0 was 35 days 16 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on [SEA/IND] Badnaam 2.0?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod) are the tags [SEA/IND] Badnaam 2.0 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [SEA/IND] Badnaam 2.0 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [SEA/IND] Badnaam 2.0 among them: 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.
Map and rules
Which rules does [SEA/IND] Badnaam 2.0 enforce, and what are its settings?
You will find no gather rate in the name of [SEA/IND] Badnaam 2.0. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [SEA/IND] Badnaam 2.0 uses?
[SEA/IND] Badnaam 2.0 runs a game-generated procedural map at size 3,750, seed 1337. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Getting in
How do you get onto [SEA/IND] Badnaam 2.0?
To connect, start Rust, press F1, and type client.connect 103.212.136.180:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://chernobyl.in/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is 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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).