[SEA/IND] Badnaam 2.0

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 30d ago · 103.212.136.191:28015

Abstract

We describe the public Rust server [SEA/IND] Badnaam 2.0, reached at 103.212.136.191:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #12,720 of all servers, the top 53%. It last wiped 33d ago.

Keywordsoxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	2/100	2% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#12,720	top 53%
Last wipe	33d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

Figure 2: 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.

4Rank

The server stands in the top 53% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
No wipe seen yet.

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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Custom map, no picture published

Figure 4: The map: Custom Map.

Table 3: The server's published settings.

Address	`103.212.136.191:28015`
Region	–
Max players	100
Group limit	8, the default
Wipe schedule	–
Last wipe	25 Sep 2026, 12:55 UTC
Hostname	–
First seen	25 Sep 2026
Map	Custom Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are busiest community rust servers [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average	447/450
Japan Tokyo - Main\|10/23\|JP/KR/SEA\|金曜日\|JumpRust.comEA · groups of 16+ · weekly · 119 on average	21/550
Rustoria.co - SEA LongEA · groups of 12+ · monthly · 106 on average	84/200
Rustafied.com - SEA MainEA · groups of 16+ · weekly · 87 on average	131/450
Rustoria.co - SEA Medium \| JUST WIPED 29.10EA · no group limit · 65 on average	51/100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA\|初心者]EA · groups of 8+ · weekly · 53 on average	14/200

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is [SEA/IND] Badnaam 2.0 based?

Without a region tag from [SEA/IND] Badnaam 2.0, its name still points to Asia. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 103.212.136.191:28015.

A.2What is the online status and reliability of [SEA/IND] Badnaam 2.0?

[SEA/IND] Badnaam 2.0 is currently offline, with the last sighting 30 days 7 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. The first record of it by Rust Statistics dates to 25 September 2026.

A.3What is the Rust version for [SEA/IND] Badnaam 2.0?

Rust network protocol 2633 and build 165217 is the version that [SEA/IND] Badnaam 2.0 runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4On what cycle does [SEA/IND] Badnaam 2.0 wipe?

The record of [SEA/IND] Badnaam 2.0's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 33 days 19 hours have passed since the current world was generated.

Player count

A.5How does [SEA/IND] Badnaam 2.0 compare with other Rust servers in the rankings?

Ranked by player hours across seven days, [SEA/IND] Badnaam 2.0 holds #12,720, in the top 53% of all ranked servers.

A.6At what level does [SEA/IND] Badnaam 2.0 operate in terms of players?

At this moment [SEA/IND] Badnaam 2.0 is offline, having last been seen 30 days 7 hours ago.

Tags and filters

A.7What is the meaning of the tags on [SEA/IND] Badnaam 2.0?

gmrust (Game mode): Rust survival, in its standard form; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): Your game must run protocol 2633 to connect; cs165217 (Build): The game build is 165217; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): A region code has not been set; ^o (Oxide): Plugins are handled by Oxide (uMod): these are the tags [SEA/IND] Badnaam 2.0 publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.8Where can [SEA/IND] Badnaam 2.0 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that [SEA/IND] Badnaam 2.0 fits are: Rust community servers, measured. It appears under the following filters 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.

Rules, settings, map

A.9Under what rules and settings does [SEA/IND] Badnaam 2.0 operate?

The name of [SEA/IND] Badnaam 2.0 states no gather rate. At 8 players, the group limit equals the game's default. The mode is survival, which means the standard mode, in which you gather, build and raid. Players may raid and fight one another. The server browser lists it under Community. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.

Connection

A.10What is the process for joining [SEA/IND] Badnaam 2.0?

Press F1 inside Rust to open the console and enter client.connect 103.212.136.191:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp100,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Rust survival, in its standard form.
`mp100`	Max players. The slot count is 100.
`ts8`	Group limit. Teams are limited to 8, as the game defaults.
`v2633`	Protocol. Your game must run protocol 2633 to connect.
`cs165217`	Build. The game build is 165217.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. A region code has not been set.
Mods and access
`^o`	Oxide. Plugins are handled by 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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.