Holds a respectable place: #6,446 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
9/ 100
F
Lost ground: down 5,346 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (B−); wipes are 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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 29% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
····W··
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap6.6 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak52players, last three wipes
crowd held0%else halves by day 3.5
The first 48 hours of its last wipes
Fri 9 OctFri 2 OctFri 25 Sep
Players each hour, from the hour of the wipe. The latest peaked at 60, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 9 Oct, 12:32 UTC20d ago
60
–
running
4
Fri 2 Oct, 12:00 UTC27d ago
48
halved by day 3
7 days
0
Fri 25 Sep, 21:16 UTC33d ago
48
halved by day 4
6.6 days
41
Fri 25 Sep, 12:55 UTC33d ago
84
–
0.3 days
18
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
Which region is [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) based in?
You'll find no region listed by [IND] Chernobyl - Vanilla (Previously Badnaam 2.0). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 103.212.136.191:28015 is the address to use.
How reliable is [IND] Chernobyl - Vanilla (Previously Badnaam 2.0), and is it up?
You cannot join now: [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is offline, last seen 19 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 22 September 2026, Rust Server Score saw it for the first time.
What Rust version is [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) on?
Rust network protocol 2634 and build 167398 on Linux is what [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) reset?
There is no next wipe to predict on [IND] Chernobyl - Vanilla (Previously Badnaam 2.0), as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 20 days.
What happens on [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) when wipe day arrives?
The average peak on its recent wipes was 52 players. The crowd on the latest wipe was largest 3 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 3.5 in the wipes where it did not hold.
Player numbers
Where does [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) place in the wider field of Rust servers?
Over the last seven days, [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) has #6,446 for player hours, in the top 29% of all ranked servers.
How many players does [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) usually have?
It has been 19 days 20 hours since [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on [IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): Build number: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod) are the tags [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
These Rust Server Score lists count [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
Rules and settings
How is [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) set up, and what rules does it keep?
Nothing in the name of [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) states a gather rate. 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. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on [IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
The game generates the procedural map on [IND] Chernobyl - Vanilla (Previously Badnaam 2.0) at size 3,750 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Custom Map.
Connecting
How do you get onto [IND] Chernobyl - Vanilla (Previously 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. You can find its website at https://chernobyl.in.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildBuild number: 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: 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 (B−); wipes are the one to work on (F).