A147/ 245 players
Modded#15,986
PolarBearFightClub2.0
Online 72.9.145.13:28015 checked 11m ago
moddedoxide
players now0of 50 slots
7-day average0peak –
rank#15,986top 71%
last wipe · restocked101d agono schedule published
next wipe · restock–no wipe seen yet
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 bestRankRank in region
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
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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A290/ 100 players
A320/ 1000 players
B17/ 1000 players
B230/ 700 players
B328/ 200 players
On the back of the pack
Quick answers
From the figures on this page.
Tags & lists
What is the meaning of the tags on PolarBearFightClub2.0?
The server browser reads these tags that PolarBearFightClub2.0 publishes: gmrust (Game mode): Rust survival, the standard way; mp50 (Max players): Room for 50; ts8 (Group limit): Teams cap at 8, the standard game limit; v2631 (Protocol): To join, your game version must line up with protocol 2631; cs156812 (Build): Game build: 156812; ptrak (Networking): This is the standard RakNet layer the game uses; $r? (Region code): Region code not set; ^o (Oxide): It uses Oxide (uMod) for plugins; ^z (Modded): Modded: plugins or settings change how it plays. Player numbers, queue length and world age are tagged as well, and they sit at the top of this page.
Where does PolarBearFightClub2.0 appear in the lists and filters on Rust Vending Machine?
The Rust Vending Machine lists that feature PolarBearFightClub2.0 are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What map is in play on PolarBearFightClub2.0?
The map on PolarBearFightClub2.0 is procedural, size 3,500 with seed 518502043, generated by the game. You can view it on RustMaps from this page, since the same size and seed give the same map.
Which settings and rules apply on PolarBearFightClub2.0?
The name of PolarBearFightClub2.0 gives no gather rate. 8 players is the default group size, and that is the cap here. This server runs survival, the usual game of gathering, building and raiding. Fighting and raiding between players is allowed. Plugins or settings change the game, so it is listed under Modded. Oxide plugins are running on it. The server has VAC, Valve's anti-cheat, switched on.
Server details
Where can you find PolarBearFightClub2.0?
No region is published by PolarBearFightClub2.0. A server's stated location is what Rust Vending Machine shows; the actual machine location is not looked up. You can reach it at 72.9.145.13:28015.
How reliable is PolarBearFightClub2.0, and is it online now?
The shelves show PolarBearFightClub2.0 in stock and online right now. By its own uptime report, the last restart was about 10 hours ago. 168 of 168 hours online over the last 7 full days, or 100% uptime. The first sighting of it on Rust Vending Machine was 13 September 2026.
Is PolarBearFightClub2.0 lag-free?
Over the last 48 hours the average server fps was 154, with a low of 2. Up to 73,117 entities were in play, buildings, deployables and the rest of the world combined. Memory use peaked at 2,152 MB. Lag, as players feel it, is low fps plus a growing entity count.
What version does PolarBearFightClub2.0 use?
Rust network protocol 2631 and build 156812 on Windows is what powers PolarBearFightClub2.0. To get in, your game must match the protocol; Steam keeps that updated.
Population
How does PolarBearFightClub2.0 compare to other Rust servers in the rankings?
The last seven days of player hours place PolarBearFightClub2.0 at #15,986, in the top 71% of all ranked servers.
What is the current player count on PolarBearFightClub2.0?
PolarBearFightClub2.0 is carrying 0 players on 50 slots at the moment. The seven-day average stands at 0 players.
Wipe details
How often does PolarBearFightClub2.0 wipe?
The wipes of PolarBearFightClub2.0 on record are too few to show its rhythm. The next force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. It has been running its current world since 101 days 19 hours ago.
Getting in
What is the way to join PolarBearFightClub2.0?
Open Rust and press F1 for the console, then type client.connect 72.9.145.13:28015. Or use the Launch Rust button here to open the game through Steam and connect.
Server tags
what each one meansPublished as mp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z
Game
gmrust
Game mode Rust survival, the standard way.
mp50
Max players Room for 50.
ts8
Group limit Teams cap at 8, the standard game limit.
v2631
Protocol To join, your game version must line up with protocol 2631.
cs156812
Build Game build: 156812.
ptrak
Networking This is the standard RakNet layer the game uses.
$r?
Region code Region code not set.
Mods and access
^o
Oxide It uses Oxide (uMod) for plugins.
^z
Modded Modded: plugins or settings change how it plays.
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.