Rust StatisticsWorking papers on every public Rust server · 38,377 players now

PolarBearFightClub2.0

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 6m ago · 72.9.145.13:28015

Abstract

We describe the public Rust server PolarBearFightClub2.0, reached at 72.9.145.13:28015. At the last check it held 0 of 50 places, against a seven-day mean of 01. It ranks #15,412 of all servers, the top 69%. It last wiped 116d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/500% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,412top 69%
Last wipe116d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123411:0019:0004:0012:0021:0005:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
010020030040011:0019:0004:0012:0021:0005:00
Figure 2: 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of PolarBearFightClub2.0
Figure 4: The map: Procedural Map, size 3500, seed 518502043. Open on RustMaps.
Table 3: The server's published settings.
Address72.9.145.13:28015
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe4 Jul 2026, 03:36 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size3500
Seed518502043

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and upcoming Rust wipes [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 156 on average98/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average120/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average107/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average42/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average5/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average16/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of PolarBearFightClub2.0 smooth?

Its average server fps over the last 48 hours was 120, with a minimum of 71. Its entity count reached a maximum of 73,585, including buildings, deployables and all other world objects. Memory use peaked at 2,183 MB. When fps is low and entity count climbs, players feel lag.

A.2What location does PolarBearFightClub2.0 have?

A region is not published by PolarBearFightClub2.0. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 72.9.145.13:28015 is its address.

A.3What is the online status and reliability of PolarBearFightClub2.0?

PolarBearFightClub2.0 is online at this time. Based on the uptime it reports, the last restart occurred about 18 hours ago. The server was up 94% of the time over the last 7 full days, 158 of 168 hours. Its first appearance in Rust Statistics's records is 13 September 2026.

A.4What is the Rust version for PolarBearFightClub2.0?

The version of Rust on PolarBearFightClub2.0 is network protocol 2631 and build 156812, and the operating system is Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5When are wipes carried out on PolarBearFightClub2.0?

The record of PolarBearFightClub2.0's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 116 days 3 hours ago.

Player count

A.6What position does PolarBearFightClub2.0 occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts PolarBearFightClub2.0 at #15,412, within the top 69% of ranked servers.

A.7How would you characterise the player activity on PolarBearFightClub2.0?

On PolarBearFightClub2.0, 0 of the 50 slots are occupied at present. The seven-day average for this server is 0 players.

Tags and filters

A.8What do the tags associated with PolarBearFightClub2.0 signify?

gmrust (Game mode): Rust survival, in its standard form; mp50 (Max players): It offers 50 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2631 (Protocol): Joining requires the same game version: protocol 2631; cs156812 (Build): Build 156812 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags PolarBearFightClub2.0 publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can PolarBearFightClub2.0 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that PolarBearFightClub2.0 fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.10What are the settings and rules that govern PolarBearFightClub2.0?

The name of PolarBearFightClub2.0 states no gather rate. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is gather, build and raid: the standard game. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.

A.11On which map does PolarBearFightClub2.0 take place?

Generated by the game from seed 518502043, the procedural map on PolarBearFightClub2.0 measures 3,500. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.12What steps are required to join PolarBearFightClub2.0?

Press F1 inside Rust to open the console and enter client.connect 72.9.145.13:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp50Max players. It offers 50 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2631Protocol. Joining requires the same game version: protocol 2631.
cs156812Build. Build 156812 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. The game is altered by plugins or settings, so 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.