PolarBearFightClub2.0
Online 72.9.145.13:28015 checked 7m 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 69% 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.
Settings and map
On PolarBearFightClub2.0, which rules and settings apply?
You will find no gather rate in the name of PolarBearFightClub2.0. 8 players per group is the default limit. The server runs survival, gather, build and raid: the standard game. PvP and raiding are allowed. The server browser lists it under Modded; plugins or settings alter the game. Filed under plugins: Oxide. VAC is on: Valve's anti-cheat is enabled.
What is the map on PolarBearFightClub2.0?
PolarBearFightClub2.0 runs a procedural map of size 3,500 with seed 518502043, generated by the game. You can view the map on RustMaps from this page, as the same size and seed give the same map.
Tags
On Rust Server Index, which lists and filters carry PolarBearFightClub2.0?
These lists on Rust Server Index take PolarBearFightClub2.0: Modded Rust servers, filed by play style. Filed under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags listed for PolarBearFightClub2.0?
These are the tags PolarBearFightClub2.0 publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2631 (Protocol): Joining needs you on game protocol 2631; cs156812 (Build): The game build here is 156812; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): The region code field is left empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Plugins or changed settings put this under Modded. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipes and resets
Which wipe timetable does PolarBearFightClub2.0 follow?
The record holds too few of PolarBearFightClub2.0's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Its present world dates from 115 days 22 hours.
Player counts
How is PolarBearFightClub2.0 ranked compared with the rest?
Filed under rankings: #15,414 for PolarBearFightClub2.0 on seven-day player hours, top 69% overall.
What does the player count on PolarBearFightClub2.0 look like?
PolarBearFightClub2.0 is currently showing 0 players on 50 slots. 0 players is the average over the past seven days.
Server facts
What Rust version is PolarBearFightClub2.0 on?
Rust network protocol 2631 and build 156812, on Windows, is what PolarBearFightClub2.0 runs. To join you need the same protocol; Steam handles the update.
How reliable is PolarBearFightClub2.0, and is it online now?
Right now PolarBearFightClub2.0 is up and running. About 13 hours ago, by its own uptime figure, is when it last restarted. It was up 158 of 168 hours across the last 7 full days, or 94% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
How well does PolarBearFightClub2.0 perform?
The last 48 hours give an average of 123 server fps and a floor of 71. The entity count reached 73,499, covering buildings, deployables and all else in the world. The peak memory figure stood at 2,064 MB. Lag, to players, is low fps and an entity count that climbs.
What is the location of PolarBearFightClub2.0?
PolarBearFightClub2.0 gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 72.9.145.13:28015.
Joining the server
What is the way onto PolarBearFightClub2.0?
Two ways in. Type client.connect 72.9.145.13:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z
Game
gmrust
mp50
ts8
v2631
cs156812
ptrak
$r?
Mods and access
^o
^z
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.