Offline 179.100.122.231:28015 checked 25d ago
Battlegrounds Teamplay
Connect
srv = rust.server("179.100.122.231: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 2 Oct. 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 best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 12:25 UTC26d ago | 0 | NaN | running | 0 |
# 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
4000 · seed 134678
- map
- Procedural Map
- size
- 4000
- seed
- 134678
Server
srv.info()- address
- 179.100.122.231:28015
- region
- –
- max players
- 20
- group limit
- 64 max
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 12:25 UTC
- hostname
- –
- first seen
- 2 Oct 2026
About this server · in its own words
print(srv.description)
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 · 151 on average | 120/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 75/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population data
How does Battlegrounds Teamplay compare in the rankings?
Rank #16,009 on seven-day player hours for Battlegrounds Teamplay, within the top 71% of all ranked servers.
What population does Battlegrounds Teamplay carry?
Battlegrounds Teamplay returns no live count at this refresh, having last been seen 25 days 5 hours ago.
Server facts
What is the Rust version on Battlegrounds Teamplay?
The build is Rust network protocol 2634 and build 166652 on Linux, run by Battlegrounds Teamplay. Joining needs the same protocol on your game; Steam handles the update.
Is Battlegrounds Teamplay up, and what does its uptime show?
Offline now for Battlegrounds Teamplay, last seen 25 days 5 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 2 October 2026.
Where does Battlegrounds Teamplay sit?
For Battlegrounds Teamplay, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 179.100.122.231:28015.
Map and rules
Which rules apply on Battlegrounds Teamplay, and what settings?
You will not find a gather rate in the string Battlegrounds Teamplay. Group size tops out at 64 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
Which map has Battlegrounds Teamplay loaded?
Size 4,000, seed 134678: the procedural map on Battlegrounds Teamplay, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Battlegrounds Teamplay wipe, and how often?
Too few wipes are on record for Battlegrounds Teamplay to reveal its 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 26 days 6 hours ago, and that is the one in play.
On Battlegrounds Teamplay, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain Battlegrounds Teamplay?
The Rust Data lists that Battlegrounds Teamplay fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Battlegrounds Teamplay?
The game's server browser reads these tags from Battlegrounds Teamplay: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts64 (Group limit): Team size tops out at 64; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into Battlegrounds Teamplay?
The manual route: launch Rust, F1, then client.connect 179.100.122.231:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.
