LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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.
The record holds too few of PolarBearFightClub2.0's wipes to reveal its rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 116 days 18 hours.
On Rust Live Stats, PolarBearFightClub2.0 is listed under Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The slot count is 50; ts8 (Group limit): Team cap: 8, which is the game default; v2631 (Protocol): Join only if your game is on protocol 2631; cs156812 (Build): This server runs game build 156812; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): The server sets no region code; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Plugins or settings changes put this under Modded, which PolarBearFightClub2.0 publishes. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
0 of PolarBearFightClub2.0's 50 slots are filled right now. Across the past week the average was 0 players.
Player hours over seven days put PolarBearFightClub2.0 at #15,339, in the top 69% of all ranked servers.
The name PolarBearFightClub2.0 carries no gather rate. The default applies: 8 players to a group. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Modded is its browser category, where plugins or settings change the game. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
A procedural map of 3,500 with seed 518502043, generated by the game, runs on PolarBearFightClub2.0. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on PolarBearFightClub2.0 states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. Connect to 72.9.145.13:28015.
The average server fps was 121 over the last 48 hours; the lowest was 71. Buildings, deployables and everything else in the world added up to a maximum of 73,858 entities. Up to 2,183 MB of memory was used. A climbing entity count and low fps are felt as lag by players.
PolarBearFightClub2.0 operates on Windows with Rust network protocol 2631 and build 156812. Joining requires the same protocol on your game; Steam takes care of updating it.
PolarBearFightClub2.0 is up and running at this moment. About 9 hours ago is when it last restarted, according to its uptime. 158 of 168 hours were online in the last 7 full days, giving 94% uptime. The first sighting by Rust Live Stats was on 13 September 2026.
Enter client.connect 72.9.145.13:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.