[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)
Offline 103.212.136.191:28015 checked 27d ago
Server instruments
no direct query in 48 hoursPlayers now
1% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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
the same kind of game, then region, group limit, rate and wipes- 441/450
- 29/550
- 70/200
- 254/450
- 78/100
- 23/200
Quick answers
from the figures on this pageReset cycle
What happens on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.
How often does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) wipe, and when?
The rhythm of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)'s wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 27 days 3 hours ago.
Lists and filters
Which tags does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166586 (Build): Game build reading: 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod from [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0). Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
Rust Metrics lists featuring [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0): Rust community servers: live readings. Reading: server list filters. It comes up under Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
Player count
What position does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) hold among Rust servers?
Player hours over seven days put [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) at #14,669, in the top 64% of all ranked servers.
What player count does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) carry?
Status for [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0): offline. Last seen 27 days 2 hours ago.
Server details
Where does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) sit?
Check: location. No region tag comes from [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), but the name points to Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 103.212.136.191:28015.
What Rust version is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) on?
Rust network protocol 2634 and build 166586 on Linux is the build [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) runs. Check: protocol. To join, your game must match; Steam handles the update.
Is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) up, and how often does it stay up?
Check: connection. [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is offline at this moment. Last contact was 27 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 1 October 2026.
Map and rules
What settings and rules apply on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
No gather rate appears in the name: [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0). The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
Join
How can you get onto [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
Press F1 in Rust and enter client.connect 103.212.136.191:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.