On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,414top 69%
Last wipe115d agono schedule published
Next wipe–no wipe 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 50 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,414 on player hours.
Uptimehours on the list, last 48
77/ 100
B
Missed a few lessons: on the list 37 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 124 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 241 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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. 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
PolarBearFightClub2.0 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 72.9.145.13:28015.
How dependable is PolarBearFightClub2.0, and is it online at the moment?
The server is up: PolarBearFightClub2.0 is online now. The uptime it reports puts the last restart at about 12 hours ago. It was up 94% of the time over the last 7 full days, 158 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does PolarBearFightClub2.0 perform well?
It averaged 124 server fps over the last 48 hours, with a low of 71. Up to 73,499 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,064 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is PolarBearFightClub2.0 on?
You will find PolarBearFightClub2.0 on Rust network protocol 2631 and build 156812, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does PolarBearFightClub2.0 reset?
There are too few wipes on record for PolarBearFightClub2.0 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 115 days 21 hours.
Player numbers
Where does PolarBearFightClub2.0 place in the wider field of Rust servers?
Over the last seven days, PolarBearFightClub2.0 has #15,414 for player hours, in the top 69% of all ranked servers.
How many players does PolarBearFightClub2.0 usually have?
With 50 slots available, PolarBearFightClub2.0 currently has 0 players. For the last seven days, the average number of players was 0.
Tags
What is meant by the tags on PolarBearFightClub2.0?
You'll see PolarBearFightClub2.0 tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2631 (Protocol): The game protocol is 2631, so your game must match that version to join; cs156812 (Build): Build number: 156812; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. 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 Rust Server Score filters and lists feature PolarBearFightClub2.0?
Rust Server Score lists that include PolarBearFightClub2.0: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on PolarBearFightClub2.0?
The name of PolarBearFightClub2.0 gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
PolarBearFightClub2.0 runs which map?
A procedural map of size 3,500 and seed 518502043, generated by the game, is what PolarBearFightClub2.0 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join PolarBearFightClub2.0?
To connect, start Rust, press F1, and type client.connect 72.9.145.13:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2631
ProtocolThe game protocol is 2631, so your game must match that version to join.
cs156812
BuildBuild number: 156812.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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 performance (A+); population is the one to work on (F).