Online72.9.145.13:28015checked 10m ago
PolarBearFightClub2.0
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
daily · 1 is bestTop 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
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which rules govern PolarBearFightClub2.0?
A gather rate is absent from the name of PolarBearFightClub2.0. The group limit is the game's default of 8 players. The server runs survival, gather, build, raid: the standard game. Fighting and raiding between players is allowed. The server browser lists it under Modded, because plugins or settings alter the game. Plugins: Oxide. Anti-cheat VAC from Valve is on.
What is the map on PolarBearFightClub2.0?
A procedural map of size 3,500 is what PolarBearFightClub2.0 runs, generated by the game with seed 518502043. You can see it on RustMaps from this page, because the same size and seed give the same map.
Tags and filters
Where can PolarBearFightClub2.0 be found in Rust Player Count lists and filters?
The Rust Player Count lists that PolarBearFightClub2.0 fits 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.
What information do the tags on PolarBearFightClub2.0 convey?
These are the tags PolarBearFightClub2.0 publishes for the game's server browser: gmrust (Game mode): Survival as standard in Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team, which is what the game sets by default; v2631 (Protocol): Joining requires the same protocol: 2631; cs156812 (Build): Build number: 156812; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): A region code is not present; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): This server is Modded; plugins or settings affect how it plays. The tags also include its current players, its queue and when its world was made, shown at the top of this page.
Player numbers
What is the player count on PolarBearFightClub2.0?
Right now, 0 players are on PolarBearFightClub2.0, which has 50 slots. The average player count for the past seven days is 0.
What position does PolarBearFightClub2.0 hold among Rust servers?
Over the last seven days, PolarBearFightClub2.0 is #15,966 for player hours, placing it in the top 72% of ranked servers.
About the server
What is the online status and reliability of PolarBearFightClub2.0?
PolarBearFightClub2.0 is currently online. The uptime it gives suggests it restarted about 20 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. Its first appearance in Rust Player Count was on 13 September 2026.
What Rust version is used on PolarBearFightClub2.0?
Windows hosts PolarBearFightClub2.0, which runs Rust network protocol 2631 and build 156812. The protocol has to match for you to join, but Steam updates it without any action from you.
What is the location of PolarBearFightClub2.0?
There is no region published by PolarBearFightClub2.0. Where a server says it is, that is what Rust Player Count shows; it does not check the machine's actual location. It is located at 72.9.145.13:28015.
Is PolarBearFightClub2.0 lag-free?
The server ran at an average of 157 fps over the last 48 hours, never falling below 2. The highest entity count was 73,117, covering buildings, deployables and all other objects. At its highest, it used 2,152 MB of memory. What players perceive as lag comes from low fps and a rising entity count.
Wipe schedule
What wipe pattern does PolarBearFightClub2.0 follow?
The rhythm of wipes on PolarBearFightClub2.0 cannot be told yet, since too few are on record. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it comes next. It has been running its current world for 102 days 4 hours.
Connect to the server
How can I connect to PolarBearFightClub2.0?
Joining is done by opening the console (F1) and running client.connect 72.9.145.13:28015. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in.
Server tags
what each one meansPublished 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.