Online 72.9.145.13:28015 checked 12m ago
PolarBearFightClub2.0
Connect
srv = rust.server("72.9.145.13:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
3500 · seed 518502043
- map
- Procedural Map
- size
- 3500
- seed
- 518502043
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 164 on average | 119/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 119/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 27/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 114/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 34/1000 |
Quick answers
From the figures on this page.
Player counts
What position does PolarBearFightClub2.0 take in the server rankings?
Player hours over seven days put PolarBearFightClub2.0 at #15,404, in the top 69% of the ranked set.
What population does PolarBearFightClub2.0 carry?
PolarBearFightClub2.0 reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players.
About the server
How well does PolarBearFightClub2.0 perform?
The 48-hour average is 123 server fps, with a low of 71. Entity numbers reached 73,484, and that includes buildings, deployables and the rest. Memory peaked at 2,064 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on PolarBearFightClub2.0?
Rust network protocol 2631 and build 156812 on Windows is what PolarBearFightClub2.0 runs. The protocol has to match before you can join, and Steam does the updating.
Is PolarBearFightClub2.0 up, and what does its uptime show?
PolarBearFightClub2.0 reports itself online at the current refresh. A restart about 9 hours ago is what its reported uptime implies. Uptime of 90% across the last 7 full days: 152 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does PolarBearFightClub2.0 run from?
There is no region published for PolarBearFightClub2.0. Rust Data 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.
Settings and map
What rules and settings are recorded for PolarBearFightClub2.0?
The name PolarBearFightClub2.0 carries no gather rate. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on PolarBearFightClub2.0?
PolarBearFightClub2.0 runs a procedural map of size 3,500 with seed 518502043, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does PolarBearFightClub2.0 wipe, and on what schedule?
The record for PolarBearFightClub2.0 holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 115 days 18 hours ago, and that is the one in play.
Lists and tags
Which Rust Data filters and lists contain PolarBearFightClub2.0?
These Rust Data lists include PolarBearFightClub2.0: 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.
Which meanings do the tags on PolarBearFightClub2.0 hold?
These tags are published by PolarBearFightClub2.0 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2631 (Protocol): The server speaks protocol 2631, so match your game version; cs156812 (Build): Recorded game build: 156812; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join PolarBearFightClub2.0?
The manual route: launch Rust, F1, then client.connect 72.9.145.13:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.