RUST METRICSFlight deck · live data
Data live Servers11,693 Players37,607 Populated2,934 Fresh wipes 3 h91 Scan5 min
‹ All servers84.74.65.236:28015
Online Full Queue Fresh wipe Wipe due No query

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

Online 84.74.65.236:28015 checked 12m ago

COM 1 · connect

Server instruments

last reading Thu 01:00 UTC
0 6 12 19 25 PAX 0 /25

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 39 SERVER FPS

Server fps

48 h low 36 · below 20 is lag, below 10 is bad
0 100 200 300 400 ENT 199,734 ×1000

Entities

48 h range 197,467–200,049 · memory 6,976 MB
1239 ET SINCE RESTART 11D 20H

Uptime

11 days 20 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,353top 69%
Last wipe11d agono schedule published
Next wipe–too few wipes seen yet
Memory6,976MBat the last reading
REC 1

Players

AveragePeak
0123403:0012:0022:0006:0015:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608003:0012:0022:0006:0015:0001: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 04:54 UTC11d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

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

To tell the rhythm of Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 11 days 21 hours ago.

Tags

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

Tags published by Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp25 (Max players): 25 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

On Rust Metrics, Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

Where does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] sit in the rankings?

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

What player count does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] carry?

Current headcount on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]: 0 players, 25 slots available. A seven-day average of 0 players is the reading.

Server details

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

Reading: location. Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 84.74.65.236:28015.

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

Version check: Rust network protocol 2634 and build 167781 on Windows, run by Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Over the last 48 hours the average was 45 server fps; the floor was 36. Reading: 200,049 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 6,976 MB. Expect lag when fps falls and entities climb.

How reliable is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], and is it online now?

Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] reports online. Status: normal. Reading: uptime. About 11 days 20 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 166 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What settings and rules apply on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Check: gather rate. The name Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

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

Size 6,000 and seed 25665: the game generates the procedural map on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

How do you connect to Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?

Check: join. Open Rust, press F1, then enter client.connect 84.74.65.236:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp25
Max players 25 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Game build reading: 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.