On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 250% full
7-day average0peak –
Rank#15,412top 69%
Last wipe11d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 25 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,412 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
76/ 100
B
Mostly smooth: 46 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 239 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?
Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 84.74.65.236:28015.
How reliable is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE], and is it up?
You can join now: Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] is online. The uptime it reports puts the last restart at about 11 days 1 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] perform well?
It averaged 46 server fps over the last 48 hours, with a low of 35. At its peak, it held 200,049 entities, including buildings, deployables and all else in the world. Memory use reached up to 6,473 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] sit?
You will find Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] on Rust network protocol 2634 and build 167781, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] wipe its map?
Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 11 days 2 hours.
What happens on Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] when wipe day arrives?
Recent wipes have peaked at 0 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] place in the wider field of Rust servers?
Over the last seven days, Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] has #15,412 for player hours, in the top 69% of all ranked servers.
Is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] a busy server?
With 25 slots available, Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] currently has 0 players. A seven-day average of 0 players applies here.
Tags
What do Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp25 (Max players): 25 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE]?
These Rust Server Score lists count Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] set up, and what rules does it keep?
The name of Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] runs which map?
A procedural map of size 6,000 and seed 25665, generated by the game, is what Bengal Play [Decay Off | Whitelist | SWISS | Max. SIZE] runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
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 after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp25,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp25
Max players25 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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.
A term to build on. Strongest in uptime (A+); population is the one to work on (F).