Station XX-14669 · no signal
[SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)
Offline 103.212.136.191:28015 checked 27d ago
- Players now
- 1/ 100
- 1% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,669
- top 64%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 100 slots
- Motion · 24 h
- M –not enough readings
Players
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.
- usual gap
- 0.3 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 2 Oct, 12:00 UTC27d ago | M0.0▲rising | 1 | – | – | running | 0 |
| Fri 2 Oct, 05:43 UTC27d ago | M0.0▲rising | 1 | – | 0.3 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which settings and rules apply on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
No gather rate appears in the name of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0). Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) right now?
No players are recorded on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) at this moment; it is offline, and the last sighting was 27 days 2 hours ago.
How does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) rank against other Rust servers?
Over the last seven days, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) recorded enough player hours to reach #14,669 worldwide, placing it in the top 64% of all ranked servers.
Server facts
How reliably does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) stay online?
As recorded now, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) is not reachable, the last contact having been 27 days 2 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 1 October 2026 is when Rust Server Trends first recorded it.
Which region does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) run from?
No region tag comes from [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0), though the name points to Asia. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 103.212.136.191:28015 is the address it uses.
Which Rust version is [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) running?
On Linux, [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) runs Rust network protocol 2634 and build 166586. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
How often does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) wipe, and on which days?
On record so far are too few of [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)'s wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 2 hours.
Lists and tags
What do the server tags on [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) mean?
These are the tags [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166586 (Build): Game build: 166586; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0) appear?
These Rust Server Trends lists include [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0): Rust community servers without the side modes. On the server list, the filters it matches are: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
How to join
How do you connect to [SEA/IND] Chernobyl - Vanilla (Previously Badnaam 2.0)?
To join, enter client.connect 103.212.136.191:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.