RUST METRICSFlight deck · live data
Data live Servers11,722 Players55,260 Populated3,387 Fresh wipes 3 h135 Scan5 min
‹ All servers46.116.32.7:28015
Offline Full Queue Fresh wipe Wipe due No query

Bandoler's 2x Trio | Living Wipe [Testing]

Offline 46.116.32.7:28015 checked 37d ago

2x trio biweekly wipes moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 1 /100

Players now

1% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,352no region published
Last wipe37d agobiweekly schedule
Next wipe4d 10hSun 1 Nov, 09:55 UTC
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep
PLAN

Wipe schedule

Next wipe Sunday 1 November, 09:55 UTC, in 4d 10h. Biweekly: 14 days after its last wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What wipe timing does Bandoler's 2x Trio | Living Wipe [Testing] follow?

From biweekly: 14 days after its last wipe, the next wipe of Bandoler's 2x Trio | Living Wipe [Testing] is an estimate. Due on Sunday 1 November at 09:55 UTC is its next wipe. The world it runs now was made 37 days 13 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Tag meanings

Which tags does Bandoler's 2x Trio | Living Wipe [Testing] carry, and what do they mean?

Tags published by Bandoler's 2x Trio | Living Wipe [Testing], read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts3 (Group limit): Teams are capped at 3; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Bandoler's 2x Trio | Living Wipe [Testing]?

On Rust Metrics, Bandoler's 2x Trio | Living Wipe [Testing] sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. These filters bring it up on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Every two weeks; Gather rate: 2x.

Player count

What position does Bandoler's 2x Trio | Living Wipe [Testing] hold among Rust servers?

Player hours over seven days put Bandoler's 2x Trio | Living Wipe [Testing] at #14,352, in the top – of all ranked servers.

What player count does Bandoler's 2x Trio | Living Wipe [Testing] carry?

Reading for Bandoler's 2x Trio | Living Wipe [Testing]: offline at this moment; last seen 37 days 13 hours ago.

Operator and location

What location is Bandoler's 2x Trio | Living Wipe [Testing] hosted in?

No region comes from Bandoler's 2x Trio | Living Wipe [Testing]. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 46.116.32.7:28015.

What Rust version is Bandoler's 2x Trio | Living Wipe [Testing] on?

Rust network protocol 2633 and build 164530 on Windows is the build Bandoler's 2x Trio | Living Wipe [Testing] runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Bandoler's 2x Trio | Living Wipe [Testing], and is it online now?

Reading: offline. Bandoler's 2x Trio | Living Wipe [Testing] last answered 37 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 20 September 2026.

Settings and map

What rules does Bandoler's 2x Trio | Living Wipe [Testing] enforce, and what are its settings?

The name carries the rate: 2x gather on Bandoler's 2x Trio | Living Wipe [Testing]. Check: group limit. 3 players, under the name trio. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is Bandoler's 2x Trio | Living Wipe [Testing] on?

Procedural map on Bandoler's 2x Trio | Living Wipe [Testing], made by the game's generator.

Join

How do you connect to Bandoler's 2x Trio | Living Wipe [Testing]?

Check: join. Open Rust, press F1, then enter client.connect 46.116.32.7:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^z,^y,^b,gmrust,cs164530,ts3

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts3
Group limit Teams are capped at 3.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Game build reading: 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins 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.