Skip to the page
Every Rust server graded on real, live numbers. 81,308 players on the roll · 11,837 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 29 October 2026 Pupil no. 103.212.136.191:28015
Name of server

[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)

RegisterAbsentOffline
Region–
Address103.212.136.191:28015
Last checked27d ago
oxide
Launch Rust and join
Overall grade

Not there yet

43 out of 100, the average of 2 subjects

Players now 1/ 100 1% full
7-day average0peak –
Rank#14,669top 64%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average unmarked No weekly average to mark yet.
Standingrank on player hours 36/ 100 Working its way up from the back of the class: #14,669 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 50/ 100 Holding steady: up 25 places this week.

A term to build on. Strongest in momentum (D); standing 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 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
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 Oct

Top 64% 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

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.

usual gap0.3 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 12:00 UTC27d ago 1 – running 0
Fri 2 Oct, 05:43 UTC27d ago 1 – 0.3 days 0

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
Rustoria.co - SEA Main
EA · groups of 16+ · weekly · 181 on average
444 / 450
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com
EA · groups of 16+ · weekly · 119 on average
28 / 550
Rustoria.co - SEA Long
EA · groups of 12+ · monthly · 104 on average
85 / 200
Rustafied.com - SEA Main
EA · groups of 16+ · weekly · 82 on average
249 / 450
Rustoria.co - SEA Medium | JUST WIPED 29.10
EA · no group limit · 65 on average
69 / 100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]
EA · groups of 8+ · weekly · 53 on average
19 / 200

Quick answers

from the figures on this page

Server facts

Where in the world is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

The name of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) points to Asia, though no region tag is set. 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 dependable is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), and is it online at the moment?

At this moment, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is offline; the last time it was seen was 27 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.

On what Rust version does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) sit?

You will find [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) on Rust network protocol 2634 and build 166586, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.

Wipe cycle

On what schedule does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) reset?

[SEA/IND] Chernobyl - Vanilla (Previously 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. The world it runs now was created 27 days 2 hours.

What happens on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) when wipe day arrives?

Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.

Population

Where does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) sit among Rust servers?

Over the last seven days, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) has #14,669 for player hours, in the top 64% of all ranked servers.

How many players does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) usually have?

The last sighting of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) was 27 days 1 hours ago, and it is offline right now.

Lists and filters

How should you read the tags on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

You'll see [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166586 (Build): This runs on build 166586; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod) in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.

Which Rust Server Score filters and lists feature [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?

Rust Server Score lists that include [SEA/IND] Chernobyl - Vanilla (Previously 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

Which rules does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) enforce, and what are its settings?

Nothing in the name of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.

Getting in

What is the way to join [SEA/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.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o

Game

gmrust
Game mode This one runs plain Rust survival, with nothing altered.
mp100
Max players The server holds 100 slots.
ts8
Group limit A team can hold 8 at most, which is the game default.
v2634
Protocol To get in, your game needs to be on the same version: the protocol is 2634.
cs166586
Build This runs on build 166586.
ptrak
Networking RakNet handles it, the game's default network layer.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide The 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.