PolarBearFightClub2.0
72.9.145.13:28015 checked 8m ago
Players
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
Top 71% 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
| 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
Quick answers
Population
Where does PolarBearFightClub2.0 sit in the rankings?
In the top 71% of all ranked servers, PolarBearFightClub2.0 is #15,974 on player hours for the last seven days.
What is the player count on PolarBearFightClub2.0?
The current player count for PolarBearFightClub2.0 is 0, out of 50 slots. The average player count over the last seven days is 0.
Tags & Lists
PolarBearFightClub2.0 tags: what do they indicate?
The game's server browser reads these tags from PolarBearFightClub2.0: gmrust (Game mode): Rust survival, standard; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default is 8 per team; v2631 (Protocol): Your game must be on protocol 2631 to connect; cs156812 (Build): Running build 156812; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): No region code listed; ^o (Oxide): Uses Oxide (uMod) for plugins; ^z (Modded): Under Modded, because plugins or settings modify play. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Which lists and filters on BestRustServers.xyz contain PolarBearFightClub2.0?
These BestRustServers.xyz lists include PolarBearFightClub2.0: Best modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server Information
What Rust version is PolarBearFightClub2.0 on?
On Windows, PolarBearFightClub2.0 runs Rust network protocol 2631 and build 156812. Steam updates your game automatically, but it needs to match the protocol to join.
How smooth is the performance on PolarBearFightClub2.0?
Over 48 hours, it averaged 155 server fps; the lowest was 2. The entity count reached 73,117, covering buildings, deployables and all other world objects. At its highest, memory usage was 2,152 MB. What players experience as lag is low fps combined with a rising entity count.
How reliable is PolarBearFightClub2.0 and is it online?
The server is online: PolarBearFightClub2.0. About 13 hours ago is when it last restarted, based on its uptime. Over the past 7 full days, it was online 168 of 168 hours, 100% of the time. On 13 September 2026, BestRustServers.xyz saw it for the first time.
What is the location of PolarBearFightClub2.0?
No region is given by PolarBearFightClub2.0. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 72.9.145.13:28015 is its address.
Rules and Settings
What is the map on PolarBearFightClub2.0?
Generated by the game, the map on PolarBearFightClub2.0 is procedural, size 3,500, seed 518502043. On RustMaps, from this page, the same size and seed show the same map.
PolarBearFightClub2.0 rules and settings: what are they?
A gather rate is not given in the name PolarBearFightClub2.0. The default cap of 8 players per group is in force. Listed as survival, gather, build, raid: the standard game. Player combat and raiding are enabled. The Modded section of the browser holds it: plugins or settings apply. Oxide plugins are used. The server has VAC on.
Wipe Information
PolarBearFightClub2.0 wipe schedule: what does it show?
PolarBearFightClub2.0's wipe rhythm cannot be told from the wipes on record, which are too few. A force wipe, next on Thursday 5 November at 19:00 UTC, takes every Rust server with it. The current world has been running since 101 days 22 hours.
How to Join
PolarBearFightClub2.0 joining: how is it done?
Enter client.connect 72.9.145.13:28015 in the console (F1 in Rust), or use Launch Rust on this page to open Steam and connect.
Server tags
Published as mp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z
Game
gmrust- Game mode Rust survival, standard.
mp50- Max players Slots: 50.
ts8- Group limit The game default is 8 per team.
v2631- Protocol Your game must be on protocol 2631 to connect.
cs156812- Build Running build 156812.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code No region code listed.
Mods and access
^o- Oxide Uses Oxide (uMod) for plugins.
^z- Modded Under Modded, because plugins or settings modify play.
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.