Station XX-15351 · no signal
PolarBearFightClub2.0
Offline 72.9.145.13:28015 checked 4h ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,351
- top 69%
- Last wipe
- 117d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
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 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
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 map is running on PolarBearFightClub2.0?
The procedural map on PolarBearFightClub2.0 is size 3,500 with seed 518502043, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on PolarBearFightClub2.0?
No gather rate appears in the name of PolarBearFightClub2.0. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on PolarBearFightClub2.0?
No players are recorded on PolarBearFightClub2.0 at this moment; it is offline, and the last sighting was 4 hours ago. Averaged across the last seven days, the population was 0 players.
How does PolarBearFightClub2.0 rank against other Rust servers?
The last seven days of player hours place PolarBearFightClub2.0 at #15,351, in the top 69% of all ranked servers.
Server details
How reliably does PolarBearFightClub2.0 stay online?
PolarBearFightClub2.0 is down at the moment; the last recorded contact was 4 hours ago. Its reported uptime points to a restart about 13 hours ago. Of the 168 hours in the last 7 full days, it was up for 157, or 93% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
How well does PolarBearFightClub2.0 perform under load?
Across the last 48 hours it averaged 124 server fps, with a floor of 74. Buildings, deployables and all the rest of the world's entities brought it to a high of 73,858. It reached a ceiling of 2,183 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does PolarBearFightClub2.0 run from?
Nothing about a region comes from PolarBearFightClub2.0. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 72.9.145.13:28015.
What build of Rust does PolarBearFightClub2.0 use?
PolarBearFightClub2.0 is running Rust network protocol 2631 and build 156812 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
How often does PolarBearFightClub2.0 wipe, and on which days?
Too few wipes of PolarBearFightClub2.0 are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 117 days 1 hours.
Tags
What do the server tags on PolarBearFightClub2.0 mean?
These are the tags PolarBearFightClub2.0 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2631 (Protocol): Game protocol 2631: to join, your game must match this version; cs156812 (Build): It runs game build 156812; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does PolarBearFightClub2.0 appear?
The Rust Server Trends lists that take in PolarBearFightClub2.0 are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto PolarBearFightClub2.0?
Enter client.connect 72.9.145.13:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.