Rust Data

rustdata.spaceservers46.116.32.7:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 46.116.32.7:28015 checked 38d ago

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

2x trio biweekly wipes moddedcarbon

Connect

srv = rust.server("46.116.32.7:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 0 # peak –
rank #14,352 # no region published
last wipe 38d ago # biweekly schedule
next wipe 3d 21h # Sun 1 Nov, 09:55 UTC

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep23 Sep24 Sep26 Sep27 Sep

Wipe schedule

srv.wipe_schedule()

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
46.116.32.7:28015
region
–
max players
100
group limit
trio
wipe schedule
biweekly
last wipe
20 Sep 2026, 09:55 UTC
hostname
–
first seen
20 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] FULLWIPED 25.10trio · 2x · biweekly · 136 on average100/200
1HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 10 on average3/150
2HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPEDEU · trio · 2x · biweekly · 3 on average2/150
3ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ]EU · trio · 2x · biweekly · 2 on average3/150
4» ProjectGaming.gg | 2X Vanilla | Solo/Duo/Trio | WIPED 10/25trio · 2x · biweekly · 2 on average3/150
5#3 [RU] ДЛЯ НОВИЧКОВ X2|MAX3|ORP|SHOP|R7ZONE.RUEU · trio · 2x · biweekly · 1 on average1/300

Quick answers

From the figures on this page.

Player counts

What position does Bandoler's 2x Trio | Living Wipe [Testing] take in the server rankings?

Rank #14,352 on seven-day player hours for Bandoler's 2x Trio | Living Wipe [Testing], within the top – of all ranked servers.

How full does Bandoler's 2x Trio | Living Wipe [Testing] run?

The current row shows Bandoler's 2x Trio | Living Wipe [Testing] offline; the last response was 38 days 1 hours ago.

About the server

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

Version Rust network protocol 2633 and build 164530 on Windows is reported by Bandoler's 2x Trio | Living Wipe [Testing]. The protocol has to match before you can join, and Steam does the updating.

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

Bandoler's 2x Trio | Living Wipe [Testing] is offline at this refresh; the last response came 38 days 1 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 20 September 2026.

Which location does Bandoler's 2x Trio | Living Wipe [Testing] run from?

No region is published by Bandoler's 2x Trio | Living Wipe [Testing]. 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 46.116.32.7:28015.

Map and rules

Which settings and rules does Bandoler's 2x Trio | Living Wipe [Testing] run?

The name carries the figure: Bandoler's 2x Trio | Living Wipe [Testing] runs 2x gather. Up to 3 players may share a group (trio). survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. Anti-cheat status: VAC on.

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

A procedural map runs on Bandoler's 2x Trio | Living Wipe [Testing], generated by the game.

Wipe data

When does Bandoler's 2x Trio | Living Wipe [Testing] wipe, and on what schedule?

The next wipe for Bandoler's 2x Trio | Living Wipe [Testing] is an estimate, drawn from biweekly: 14 days after its last wipe. On Sunday 1 November at 09:55 UTC the next wipe is due. A new world was started 38 days 2 hours ago, and that is the one in play. A fortnightly wipe schedule is published in its tags.

Lists and tags

Which Rust Data filters and lists contain Bandoler's 2x Trio | Living Wipe [Testing]?

On Rust Data, Bandoler's 2x Trio | Living Wipe [Testing] appears in these lists: Modded Rust servers, 2x Rust servers and Trio Rust servers. 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.

How should you read the server tags on Bandoler's 2x Trio | Living Wipe [Testing]?

The game's server browser reads these tags from Bandoler's 2x Trio | Living Wipe [Testing]: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts3 (Group limit): The team cap is 3; v2633 (Protocol): To join, your game must run protocol 2633; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^b (Biweekly): The cycle is fourteen days; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

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

In Rust, F1 opens the console: type client.connect 46.116.32.7:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players 100 slots in total.
ts3
Group limit The team cap is 3.
v2633
Protocol To join, your game must run protocol 2633.
cs164530
Build Recorded game build: 164530.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly The cycle is fourteen days.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon Runs on Carbon for plugins.

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.

Rust Data 68,833 players 11,715 servers online