PolarBearFightClub2.0
Online 72.9.145.13:28015 checked 9m ago
Server instruments
last reading Wed 22:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 71 · below 20 is lag, below 10 is badEntities
48 h range 59,499–73,858 · memory 1,844 MBUptime
11 h 1 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes- 54/500
- 127/100
- 46/225
- 54/700
- 7/200
- 8/1000
Quick answers
from the figures on this pageWipe timing
When does PolarBearFightClub2.0 wipe?
To tell the rhythm of PolarBearFightClub2.0, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 116 days 19 hours ago.
Lists and filters
Which tags does PolarBearFightClub2.0 carry, and what do they mean?
These are the tags PolarBearFightClub2.0 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2631 (Protocol): Match the game version: protocol 2631 is required; cs156812 (Build): Game build reading: 156812; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does PolarBearFightClub2.0 appear in Rust Metrics lists and filters?
These Rust Metrics lists carry PolarBearFightClub2.0: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
What position does PolarBearFightClub2.0 hold among Rust servers?
Player hours over seven days put PolarBearFightClub2.0 at #15,344, in the top 69% of all ranked servers.
How full does PolarBearFightClub2.0 get?
Current headcount on PolarBearFightClub2.0: 0 players, 50 slots available. Check: player average. 0 over the last seven days.
Server
Which location does PolarBearFightClub2.0 run from?
Reading: location. PolarBearFightClub2.0 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 72.9.145.13:28015.
What Rust version is PolarBearFightClub2.0 on?
Reading: PolarBearFightClub2.0, Rust network protocol 2631 and build 156812, Windows. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on PolarBearFightClub2.0 within range?
Check: fps. Average 121 server fps over the last 48 hours, low of 71. Within range. Peak entity count: 73,858. Buildings, deployables and all else included. Memory peak: 2,183 MB. Expect lag when fps falls and entities climb.
How reliable is PolarBearFightClub2.0, and is it online now?
Reading: online. PolarBearFightClub2.0 answers right now. Reading: uptime. About 11 hours ago it restarted, on its own count. Uptime for the last 7 full days: 158 of 168 hours, or 94%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
How is PolarBearFightClub2.0 configured, and what rules are in force?
Check: gather rate. The name PolarBearFightClub2.0 does not state one. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
What map is PolarBearFightClub2.0 on?
Size 3,500 and seed 518502043: the game generates the procedural map on PolarBearFightClub2.0 from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
What do you do to join PolarBearFightClub2.0?
To join: start Rust, press F1 and type client.connect 72.9.145.13:28015. Or press Launch Rust here and Steam opens the game and connects you.