Rust Server Analytics 54,071 players11,717 servers
All servers
Drill-through Server detail

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

Online 84.74.65.236:28015 checked 10m ago

Drill-through
FilterServeris Bengal Play [Decay Off | Whitelist | SWIS…
Attributes
Last refreshed
Players now 0/ 25
7-day average 0 peak –
Rank #15,409 top 69%
Last wipe 10d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123401:0010:0019:0003:0012:0022:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
02040608001:0010:0019:0003:0012:0022: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
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule

too few wipes seen yet

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
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 04:54 UTC10d ago 0 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 520 on average 440 / 525
Rustoria.co - EU Main EU · groups of 16+ · weekly · 336 on average 25 / 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 333 on average 45 / 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 317 on average 201 / 275
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 279 on average 76 / 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 263 on average 88 / 150

Quick answers

from the figures on this page

Wipe cycle

When does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] wipe?

The rhythm of Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. The current world dates from 10 days 19 hours.

Wipe day on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]: what should you expect?

The average busiest count over recent wipes is 0 players. Peak population for the latest wipe came 0 hours after it began.

Server

Which location hosts Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

No region appears in what Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 84.74.65.236:28015.

What Rust build does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] run?

On Windows, Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] runs Rust network protocol 2634 and build 167781. Your game must match the protocol to join, and Steam applies that update.

Is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] up, and how steady is its uptime?

Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] reports online at the current check. About 10 days 17 hours ago is when it last restarted, judged by its reported uptime. 86% uptime over the last 7 full days, equal to 144 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.

Is performance on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] stable?

Over 48 hours the average held at 46 server fps, and the minimum was 35. Entity count reached 200,049, covering buildings, deployables and the rest of the world. Peak memory was 6,367 MB. Lag, for players, means low fps alongside a growing entity count.

Tags

How should the tags on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] be read?

The game's server browser reads the tags Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] publishes: gmrust (Game mode): Rust survival, standard ruleset; mp25 (Max players): 25 slots in total; ts8 (Group limit): Default team size of 8; v2634 (Protocol): To join, your game version must match protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set. 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 Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]: Community Rust servers, live. It appears on the server list under the following filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player numbers

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

The seven-day player-hours rank for Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] is #15,409, inside the top 69% of all ranked servers.

At what level does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] run its population?

Of 25 slots, 0 are filled on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] at this refresh. The seven-day mean for this server is 0 players.

Settings

How is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] configured, and what rules apply?

Gather rate is not mentioned in the name of Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]. 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. The server runs with VAC, Valve's anti-cheat, enabled.

The map on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]: which one is it?

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

Connection

How can a player join Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 84.74.65.236:28015.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard ruleset.
mp25
Max players 25 slots in total.
ts8
Group limit Default team size of 8.
v2634
Protocol To join, your game version must match protocol 2634.
cs167781
Build Game build: 167781.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been 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.