Working its way up from the back of the class: #16,001 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 952 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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 4 Oct. 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. 189.78.93.163:28015 is the address to use.
How reliable is Battlegrounds Teamplay, and is it up?
You cannot join now: Battlegrounds Teamplay is offline, last seen 24 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 4 October 2026.
What Rust version is Battlegrounds Teamplay on?
The server Battlegrounds Teamplay is on Rust network protocol 2634 and build 166652 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Battlegrounds Teamplay reset?
Battlegrounds Teamplay has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 25 days 6 hours have passed since this world was made.
Population
Where does Battlegrounds Teamplay sit among Rust servers?
In the top 71% of all ranked servers, Battlegrounds Teamplay sits at #16,001 for player hours over the last seven days.
How many players does Battlegrounds Teamplay usually have?
Battlegrounds Teamplay is offline at the moment; the last time it was seen was 24 days 3 hours ago.
Tags
What do Battlegrounds Teamplay's tags stand for?
You'll see Battlegrounds Teamplay tagged with 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): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Battlegrounds Teamplay appear in the Rust Server Score lists and filters?
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.
Rules and settings
How is Battlegrounds Teamplay set up, and what rules does it keep?
You will find no gather rate in the name of Battlegrounds Teamplay. The limit for a group is 64 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Battlegrounds Teamplay runs which map?
Battlegrounds Teamplay runs a game-generated procedural map at size 4,000, seed 134678. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto Battlegrounds Teamplay?
Enter client.connect 189.78.93.163:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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).