Rust Data

rustdata.spaceservers84.74.65.236:28016.ipynb

Run all rust-data · live

‹ All servers

Online 84.74.65.236:28015 checked 10m ago

Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]

Connect

srv = rust.server("84.74.65.236:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/25 # 0% full
7-day average 0 # peak –
rank #15,323 # top 69%
last wipe 11d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123421:0006:0016:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608021:0006:0016:0000:0009:0019:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 17 Oct, 04:54 UTC11d ago 0 NaN running 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.

display(srv.map, srv.info())

Map

6000 · seed 25665
Map of Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]
map
Procedural Map
size
6000
seed
25665
Open on RustMaps

Server

srv.info()
address
84.74.65.236:28015
region
–
max players
25
group limit
8, the default
wipe schedule
–
last wipe
17 Oct 2026, 04:54 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 552 on average596/675
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average379/525
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 299 on average47/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 298 on average37/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 271 on average133/200
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 254 on average153/300

Quick answers

From the figures on this page.

Player counts

What position does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] take in the server rankings?

Player hours over seven days put Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] at #15,323, in the top 69% of the ranked set.

How full does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] run?

The sample now reads 0 players for Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], out of 25 slots. Over the last seven days it averaged 0 players.

Server data

What does performance look like on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Server fps over the last 48 hours averages 46; the floor is 35. The entity count peaked at 200,049, covering buildings, deployables and the rest of the world. The memory field tops out at 6,473 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] on?

The build is Rust network protocol 2634 and build 167781 on Windows, run by Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]. Joining needs the same protocol on your game; Steam handles the update.

Is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] up, and what does its uptime show?

Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] reports itself online at the current refresh. Count back 11 days 11 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.

Which location does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] run from?

For Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 84.74.65.236:28015 is its address.

Settings and map

Which settings and rules does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] run?

The name Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Size 6,000, seed 25665: the procedural map on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] wipe, and on what schedule?

The record for Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 11 days 15 hours ago.

What is wipe day on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] like?

The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.

Lists and tags

Where does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] appear among Rust Data lists and filters?

The Rust Data lists that Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] hold?

Read by the game's server browser, the tags Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] publishes are: gmrust (Game mode): Rust survival in its standard form; mp25 (Max players): 25 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Enter client.connect 84.74.65.236:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp25,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp25
Max players 25 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

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.

Rust Data 79,944 players 11,805 servers online