Rust Server TrendsSeismic network · station log
Recording Stations11,854 Players99,188 Active3,861 Wipes · 3 h532 48 h

Station XX-16009 · no signal

Battlegrounds Teamplay

Offline 179.100.122.231:28015 checked 25d ago

moddedcarbon
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,009
top 71%
Last wipe
26d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16009 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 20 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k2 Oct4 Oct6 Oct7 Oct9 Oct11 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 3 Oct, 12:25 UTC26d ago M0.0steady 0 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 151 on average
81/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
130/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
144/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 96 on average
55/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 91 on average
141/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 85 on average
347/ 350
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Battlegrounds Teamplay?

The procedural map on Battlegrounds Teamplay is size 4,000 with seed 134678, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.

Which settings and rules apply on Battlegrounds Teamplay?

The name of Battlegrounds Teamplay gives no gather rate. The group limit is 64 players. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on Battlegrounds Teamplay right now?

No players are recorded on Battlegrounds Teamplay at this moment; it is offline, and the last sighting was 25 days 7 hours ago.

How does Battlegrounds Teamplay rank against other Rust servers?

On player hours for the past week, Battlegrounds Teamplay sits at #16,009, which puts it inside the top 71% of every ranked server.

Server details

How reliably does Battlegrounds Teamplay stay online?

As recorded now, Battlegrounds Teamplay is not reachable, the last contact having been 25 days 7 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 2 October 2026.

Which region does Battlegrounds Teamplay run from?

No region is published by Battlegrounds Teamplay. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 179.100.122.231:28015.

What build of Rust does Battlegrounds Teamplay use?

Rust network protocol 2634 and build 166652 on Linux is what Battlegrounds Teamplay runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on Battlegrounds Teamplay?

0 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

How often does Battlegrounds Teamplay wipe, and on which days?

Too few wipes of Battlegrounds Teamplay are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 26 days 8 hours.

Tags

What do the server tags on Battlegrounds Teamplay mean?

These are the tags Battlegrounds Teamplay publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp20 (Max players): Slots: 20; ts64 (Group limit): Each team can hold up to 64; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): It runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Battlegrounds Teamplay appear?

These Rust Server Trends lists include Battlegrounds Teamplay: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Connecting

What steps get you onto Battlegrounds Teamplay?

Enter client.connect 179.100.122.231:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166652,ts64,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp20
Max players Slots: 20.
ts64
Group limit Each team can hold up to 64.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166652
Build It runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon Carbon is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.