RS-15912Modded server
PolarBearFightClub2.0
Online 72.9.145.13:28015 checked 14m 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 72% 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
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Player activity
How populated is PolarBearFightClub2.0?
PolarBearFightClub2.0 is showing 0 players on 50 slots right now. Over the past seven days, the average player count was 0.
What is the ranking of PolarBearFightClub2.0?
On player hours across seven days, PolarBearFightClub2.0 is #15,912, inside the top 72% of all ranked servers.
Tags, lists, and filters
On Top Rust Servers, which lists and filters carry PolarBearFightClub2.0?
These Top Rust Servers lists include PolarBearFightClub2.0: Top modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What is the meaning of the tags on PolarBearFightClub2.0?
The game's server browser reads the tags that PolarBearFightClub2.0 publishes: gmrust (Game mode): Survival follows the standard Rust ruleset; mp50 (Max players): It has 50 slots; ts8 (Group limit): The team limit is 8, which is the game default; v2631 (Protocol): Protocol 2631 is required to join; your game must be on the same version; cs156812 (Build): The game build is 156812; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): No region code is assigned; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): This server is marked Modded, meaning plugins or settings alter the game. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Map and rules
What map is used on PolarBearFightClub2.0?
PolarBearFightClub2.0 runs a procedural map of size 3,500 with seed 518502043, generated by the game. The map can be seen on RustMaps from this page, as identical size and seed yield the same map.
Which settings and rules apply on PolarBearFightClub2.0?
You will not find a gather rate in the name PolarBearFightClub2.0. The group limit is the game's default of 8 players. You play survival, the normal mode where you gather, build and raid. Combat and raiding between players are allowed. It is a Modded server, meaning plugins or settings modify the game. Oxide plugins are loaded. The server runs with VAC on.
About the server
What version is PolarBearFightClub2.0 running?
On Windows, PolarBearFightClub2.0 operates Rust network protocol 2631 and build 156812. The protocol must match for you to join; Steam will update your game.
How well does PolarBearFightClub2.0 perform?
The last 48 hours saw it average 160 server fps, never going under 35. The maximum entities it carried was 72,957, covering buildings, deployables and the rest. At its highest, it consumed 2,241 MB of memory. Players feel lag when fps drops and entities increase.
What is the location of PolarBearFightClub2.0?
A region is not published by PolarBearFightClub2.0. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. 72.9.145.13:28015 is its address.
What is the uptime of PolarBearFightClub2.0?
Right now, PolarBearFightClub2.0 is up and running. Going by its reported uptime, it restarted about 15 hours ago. It spent 168 of the last 168 hours online across 7 days, giving 100% uptime. The first time Top Rust Servers saw it was on 13 September 2026.
Wipe schedule
On what schedule does PolarBearFightClub2.0 wipe?
Not enough wipe data exists yet to identify the rhythm of PolarBearFightClub2.0. The monthly force wipe applies to every Rust server; the next one is on Thursday 5 November at 19:00 UTC. The present world has been live since 103 days ago.
How to join
What are the steps to join PolarBearFightClub2.0?
To connect, start Rust, hit F1, and enter client.connect 72.9.145.13:28015. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.