Rust Data LabData lab · live
Live readings Servers11,664 Players42,799 Populated3,021 Fresh wipes · 3h89 Sampled every 5 min

Element card · group Modded · atomic number 15,411, its rank

PolarBearFightClub2.0

Online 72.9.145.13:28015 checked 9m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak –
Rank · atomic number#15,411top 69%
Last wipe115d agono schedule published
Next wipe–no wipe seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123411:0018:0002:0009:0017:0000:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
010020030040011:0018:0002:0009:0017:0000:00

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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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
  1. 1 Sh ShockRust | Bl… 32
    ShockRust | Blue | NoLimit no group limit · 161 on average 32/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 122
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 122/ 100
  3. 3 Re RETRO RUST #1 … 41
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 114 on average 41/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 28
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 87 on average 28/ 700
  5. 5 Ru RustSpain.com … 9
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 9/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 8
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average 8/ 1,000

Quick answers

from the figures on this page

Map and rules

What map is in play on PolarBearFightClub2.0?

A procedural map of size 3,500 with seed 518502043 runs on PolarBearFightClub2.0, generated by the game. The map repeats when size and seed match, and you can view it on RustMaps from this page.

How is PolarBearFightClub2.0 configured, and what rules apply?

No gather rate appears in the name of PolarBearFightClub2.0. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. Raids and player fights are part of play here. In the server browser it sits under Modded: the game is changed by plugins or settings. The plugin count is Oxide. VAC is on, Valve's anti-cheat.

About the server

What region hosts PolarBearFightClub2.0?

There is no region on record for PolarBearFightClub2.0. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 72.9.145.13:28015 is the address it uses.

Which Rust version is PolarBearFightClub2.0 on?

Rust network protocol 2631 and build 156812 on Windows is what PolarBearFightClub2.0 uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is PolarBearFightClub2.0 for staying online?

At the moment, PolarBearFightClub2.0 is online. The uptime it reports suggests it restarted roughly 13 hours ago. For the last 7 full days, 158 of 168 hours were online, giving 94% uptime. The first sighting by Rust Data Lab was on 13 September 2026.

Does PolarBearFightClub2.0 hold a steady performance?

In the last 48 hours, it averaged 123 server fps, with a low of 71. The maximum entity count was 73,499, covering buildings, deployables and all else in the world. Memory use peaked at 2,064 MB. Players feel lag when fps is low and the entity count climbs.

Wipes and resets

What is the wiping pattern on PolarBearFightClub2.0?

PolarBearFightClub2.0's wipe history on record is too thin yet to tell its rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it is running now dates from 115 days 22 hours ago.

Lists and tags

How should you read the tags on PolarBearFightClub2.0?

These are the tags PolarBearFightClub2.0 makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Player slots: 50; ts8 (Group limit): Teams cap at 8, which is the game default; v2631 (Protocol): Protocol 2631 is required; join only if your game matches it; cs156812 (Build): The game build is 156812; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): You will find it under Modded: the game is altered by plugins or settings. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does PolarBearFightClub2.0 appear in?

These themed Rust Data Lab lists carry PolarBearFightClub2.0: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player counts

How does PolarBearFightClub2.0 compare with other servers in the rankings?

Player hours over the last week put PolarBearFightClub2.0 at #15,411, inside the top 69% of ranked servers.

What does the current player count on PolarBearFightClub2.0 tell you?

PolarBearFightClub2.0 currently shows 0 players across 50 slots. The seven-day average for this server is 0 players.

Getting on

What is the way to join PolarBearFightClub2.0?

In Rust, press F1 and enter client.connect 72.9.145.13:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp50
Max players Player slots: 50.
ts8
Group limit Teams cap at 8, which is the game default.
v2631
Protocol Protocol 2631 is required; join only if your game matches it.
cs156812
Build The game build is 156812.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded You will find it under Modded: the game is altered by plugins or settings.

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.