Working its way up from the back of the class: #16,009 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 944 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players before
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 servers
classmates: the same kind of game, then region, group limit, rate and wipes
Battlegrounds Teamplay leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 179.130.125.245:28015.
Is Battlegrounds Teamplay up, and how steady is its uptime?
The server is down: Battlegrounds Teamplay is offline now, with the last sighting 25 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 4 October 2026.
What Rust version is Battlegrounds Teamplay on?
Rust network protocol 2634 and build 166652 on Linux is what Battlegrounds Teamplay runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Battlegrounds Teamplay wipe, and how often?
Battlegrounds Teamplay has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 26 days 6 hours.
Player numbers
Where does Battlegrounds Teamplay place in the wider field of Rust servers?
Over the last seven days, Battlegrounds Teamplay has #16,009 for player hours, in the top 71% of all ranked servers.
Is Battlegrounds Teamplay a busy server?
Battlegrounds Teamplay is offline at the moment; the last time it was seen was 25 days 5 hours ago.
Tags and filters
What is meant by the tags on Battlegrounds Teamplay?
The game's browser takes its cue from the tags Battlegrounds Teamplay has set: gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): The server holds 20 slots; ts64 (Group limit): A team can hold 64 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): The game build is 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Battlegrounds Teamplay?
These Rust Server Score lists count Battlegrounds Teamplay among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
What settings and rules apply on Battlegrounds Teamplay?
You will find no gather rate in the name of Battlegrounds Teamplay. The limit for a group is 64 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Battlegrounds Teamplay runs which map?
A procedural map, generated by the game, is what Battlegrounds Teamplay runs.
Getting in
How do you get onto Battlegrounds Teamplay?
To connect, start Rust, press F1, and type client.connect 179.130.125.245:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2634,gmrust,cs166652,ts64,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersThe server holds 20 slots.
ts64
Group limitA team can hold 64 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).