[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)
Offline 103.212.136.191:28015 checked 27d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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| Server | Profile | Players now |
|---|---|---|
| Rustoria.co - SEA Main | EA · groups of 16+ · weekly · 181 on average | 431 / 450 |
| Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com | EA · groups of 16+ · weekly · 119 on average | 24 / 550 |
| Rustoria.co - SEA Long | EA · groups of 12+ · monthly · 102 on average | 63 / 200 |
| Rustafied.com - SEA Main | EA · groups of 16+ · weekly · 81 on average | 207 / 450 |
| Rustoria.co - SEA Medium | JUST WIPED 29.10 | EA · no group limit · 65 on average | 62 / 100 |
| Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] | EA · groups of 8+ · weekly · 53 on average | 20 / 200 |
Quick answers
from the figures on this pageWipe cycle
When does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) wipe?
The rhythm of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) cannot yet be told: too few of its wipes are on record. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The current world dates from 27 days 4 hours.
Wipe day on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0): what should you expect?
The average busiest count over recent wipes is 1 players. The highest player count on the latest wipe arrived 0 hours in.
Server
What is the hosting location of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
Without a region tag, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) still has a name that points to Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 103.212.136.191:28015 is its address.
Which Rust version is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) on?
On Linux, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) runs Rust network protocol 2634 and build 166586. Joining requires the same protocol on your game; Steam handles the update.
What uptime does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) show, and is it up?
Offline at this refresh: [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), last seen 27 days 3 hours ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. 1 October 2026 is when Rust Server Analytics first recorded it.
Tags
Which meanings do the tags on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) carry?
The game's server browser reads the tags [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) publishes: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default team size of 8; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs166586 (Build): Build number 166586; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^o (Oxide): It runs Oxide (uMod) for plugins. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) appear across Rust Server Analytics's lists and filters?
Among the Rust Server Analytics lists [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) fits are: Community Rust servers, live. 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.
Population
Against other Rust servers, how does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) compare?
The seven-day player-hours rank for [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is #14,669, inside the top 64% of all ranked servers.
What is the population of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
The last sighting of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) was 27 days 3 hours ago; it is offline at this refresh.
Settings
What are the settings on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), and its rules?
No gather rate is given in the name of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0). The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. Community is its listing; it is a community server. Plugins from Oxide are in use. The server runs with VAC, Valve's anti-cheat, enabled.
Connection
What is the way onto [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
In the Rust console (F1), enter client.connect 103.212.136.191:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.