PolarBearFightClub2.0
72.9.145.13:28015Up, checked 6m agoMonitored since 13 Sep 2026
Health checks
from the latest readings- ReachableOn the Steam server list, checked 6m agoPassing
- Capacity0% of 50 slots in usePassing
- Queuenobody waitingPassing
- Performancerunning at 158 fpsPassing
- Fresh mapwiped 95d agoPassing
- Next wipenot predictable yetNo data
Activity
players each hour, last 48- Group limit
- 8, the default
- Wipe schedule
- not published
- Map
- Procedural Map · 3500
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- 1Survivors.gg | 2 x Vanilla | Monthlygroups of 30+ · monthly · 196 on average61 / 200
- 2404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 07.10EU · groups of 16+ · monthly · 136 on average149 / 1000
- 3ShockRust | Blue | NoLimitno group limit · 130 on average33 / 300
- 4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 06.10EU · groups of 16+ · monthly · 125 on average68 / 700
- 5404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 04.10EU · groups of 16+ · monthly · 115 on average29 / 700
- 6666 RUST /ДЛЯ НОВИЧКОВ /РОССИЯ 06.10EU · groups of 16+ · monthly · 111 on average28 / 650
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Performance
48 hours: hourly readings. 30 to 90 days: a point a day, measured since 17 Sep. Low fps and a climbing entity count mean lag.
Wipe calendar
0 days with a wipe in the last 16 weeksNot enough wipes seen yet to tell. Every server wipes at the monthly force wipe.
- No wipe seen yet.
- Address
- 72.9.145.13:28015
- Region
- –
- Max players
- 50
- Group limit
- 8, the default
- Wipe schedule
- –
- Last wipe
- 4 Jul 2026, 03:36 UTC
- Hostname
- –
- First seen
- 13 Sep 2026
Server tags
What each tag it publishes means. Published as mp50,ptrak,$r?,v2631,gmrust,cs156812,ts8,^o^z.
gmrustGame mode Standard survival, as in Rust.mp50Max players 50 player slots.ts8Group limit This is the game default: a maximum of 8 per team.v2631Protocol To join, your game needs to run protocol 2631.cs156812Build The game build is 156812.ptrakNetworking The network layer is RakNet, the game's standard.$r?Region code Region code: not set.^oOxide A plugin framework, Oxide (uMod), is in use.^zModded Plugins or settings change the game, so it is listed under Modded.Flag meanings are Facepunch's.
Player data
What is the rank of PolarBearFightClub2.0?
For player hours over seven days, PolarBearFightClub2.0 holds rank #16,700, in the top 70% of all ranked servers.
How many players are on PolarBearFightClub2.0?
With 50 slots, PolarBearFightClub2.0 holds 0 players at present. The seven-day average for players is 0.
Settings and rules
What map is used on PolarBearFightClub2.0?
PolarBearFightClub2.0 uses a procedural map of size 3,500 with seed 518502043, generated by the game. Because size and seed determine the map, a RustMaps view is available from this page.
What are the settings and rules for PolarBearFightClub2.0?
A gather rate is absent from the name PolarBearFightClub2.0. Group size follows the game default of 8 players. It runs survival, gather, build and raid: the standard game. Raiding and player-versus-player fighting are enabled. Plugins or settings change the game, and it is listed under Modded in the server browser. The plugins it uses are Oxide. The server has VAC, Valve's anti-cheat, active.
Wipe information
What wipe pattern does PolarBearFightClub2.0 follow?
Too few wipes from PolarBearFightClub2.0 are recorded to reveal a rhythm. The next force wipe is on Thursday 5 November at 19:00 UTC, and it applies to every Rust server. It has been 95 days 18 hours since the current world was made.
Tags and filters
How should you read the tags on PolarBearFightClub2.0?
gmrust (Game mode): Standard survival, as in Rust; mp50 (Max players): 50 player slots; ts8 (Group limit): This is the game default: a maximum of 8 per team; v2631 (Protocol): To join, your game needs to run protocol 2631; cs156812 (Build): The game build is 156812; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code: not set; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags PolarBearFightClub2.0 publishes; the game's server browser reads them. Shown at the top of this page are three more things from the tags: its players now, its queue and the time its world was made.
What lists and filters on Best Rust Servers hold PolarBearFightClub2.0?
The Best Rust Servers lists that PolarBearFightClub2.0 fits are: Best modded Rust servers. Filter entries for this server: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server information
What Rust version does PolarBearFightClub2.0 run?
The Rust version on PolarBearFightClub2.0 is network protocol 2631 and build 156812, running on Windows. Your game needs the same protocol to connect, and Steam updates it automatically.
Where can PolarBearFightClub2.0 be found?
There is no published region for PolarBearFightClub2.0. Best Rust Servers does not look up where the machine stands; it shows where a server says it is. You can reach it at 72.9.145.13:28015.
How smooth is PolarBearFightClub2.0?
The 48-hour average was 165 fps, with 80 as the lowest point. A maximum of 72,713 entities were present, comprising buildings, deployables and all else. The highest memory usage was 2,083 MB. Low fps and a growing entity count are the sources of lag for players.
What is the online status and reliability of PolarBearFightClub2.0?
Right now, PolarBearFightClub2.0 is up. Based on the uptime it reports, the last restart was roughly 10 hours ago. In the last 7 full days, 168 of 168 hours were online, an uptime of 100%. Best Rust Servers recorded its first appearance on 13 September 2026.
Connection
How do you connect to PolarBearFightClub2.0?
Enter client.connect 72.9.145.13:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page, which opens Rust via Steam and connects.