Skip to the page
Network live 11,829 servers online 89,289 players aboard 108 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

PolarBearFightClub2.0

Online 72.9.145.13:28015 checked 1h ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 116d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no wipe seen yet
0/ 50 players now 0% full
07-day averagepeak –
#15,426ranktop 69%
116d agolast wipeno schedule published
–next wipeno wipe seen yet
Delivery history

Players, performance and rank

Players

AveragePeak
0123419:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

05010015020019:0004:0013:0023:0008:0017: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.

Rank

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.

Wipe schedule

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

Wipes

every wipe as a delivery, newest first
  1. 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 parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 157 on average 205 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average 121 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average 183 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average 126 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average 19 / 200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average 50 / 1000
Help desk

Quick answers

From the figures on this page.

Population

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

Over the past seven days, PolarBearFightClub2.0 has climbed to #15,426 for player hours, putting it in the top 69% of all ranked servers.

Is PolarBearFightClub2.0 busy at the moment?

At the moment 0 players are on PolarBearFightClub2.0, which has 50 slots. For the last seven days the average player count was 0.

Server rules

What is the current map on PolarBearFightClub2.0?

Size 3,500 and seed 518502043 define the procedural map PolarBearFightClub2.0 runs, generated by the game. Identical size and seed give an identical map: view it on RustMaps from this page.

Which settings and rules apply on PolarBearFightClub2.0?

The name of PolarBearFightClub2.0 gives no gather rate. The game's default applies: 8 players to a group at most. It runs survival, the usual game: build, gather, raid. You can raid and fight other players. The server browser lists it as Modded, because plugins or settings alter the game. The plugins run on Oxide. The VAC anti-cheat from Valve is enabled.

About the server

In which region is PolarBearFightClub2.0 based?

You will find no region published by PolarBearFightClub2.0. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 72.9.145.13:28015.

What is the performance like on PolarBearFightClub2.0?

The 48-hour average for server fps stands at 120, never dipping below 71. The world held as many as 73,858 entities: buildings, deployables and the rest. The highest memory reading was 2,183 MB. Lag, to players, means low fps alongside an entity count on the rise.

Is PolarBearFightClub2.0 up, and how good is its uptime?

PolarBearFightClub2.0 is up and online at the moment. The uptime it reports puts its last restart at about 5 hours ago. It was up 158 of 168 hours over the last 7 full days, 94% of the time. It was first seen by Rust Wipe Tracker on 13 September 2026.

On what Rust version does PolarBearFightClub2.0 operate?

On Windows, PolarBearFightClub2.0 runs Rust network protocol 2631 and build 156812. The same protocol is required to join, and Steam takes care of updating it.

Wipe times

When does PolarBearFightClub2.0 wipe? What schedule does it follow?

Its rhythm cannot yet be told: too few of PolarBearFightClub2.0's wipes are on record. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. You are playing a world created 116 days 14 hours.

Server tags

On Rust Wipe Tracker, which lists and filters is PolarBearFightClub2.0 part of?

These Rust Wipe Tracker lists take PolarBearFightClub2.0: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

What is the meaning of the server tags on PolarBearFightClub2.0?

gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): 8 per team, which is the default; v2631 (Protocol): To join, your game must match protocol 2631; cs156812 (Build): It runs game build 156812; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings, hence the Modded listing are the tags PolarBearFightClub2.0 publishes, and the server browser takes them as read. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Getting started

How do you connect to PolarBearFightClub2.0?

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 72.9.145.13:28015.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players The server has 50 slots.
ts8
Group limit 8 per team, which is the default.
v2631
Protocol To join, your game must match protocol 2631.
cs156812
Build It runs game build 156812.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded The game is changed by plugins or settings, hence the Modded listing.

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.