Not ranked yet, so there is no place in the school to report.
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
49/ 100
D
Slipped a little: down 278 places this week. Nothing a good wipe can't fix.
A term to build on.
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
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
Next wipe Sunday 1 November, 09:55 UTC, in 3d 12h.
Biweekly: 14 days after its last 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
In what location does Bandoler's 2x Trio | Living Wipe [Testing] sit?
Bandoler's 2x Trio | Living Wipe [Testing] leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 46.116.32.7:28015.
How reliable is Bandoler's 2x Trio | Living Wipe [Testing], and is it up?
The server is down: Bandoler's 2x Trio | Living Wipe [Testing] is offline now, with the last sighting 38 days 10 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
What Rust version is Bandoler's 2x Trio | Living Wipe [Testing] on?
You will find Bandoler's 2x Trio | Living Wipe [Testing] on Rust network protocol 2633 and build 164530, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does Bandoler's 2x Trio | Living Wipe [Testing] reset?
The estimate for Bandoler's 2x Trio | Living Wipe [Testing]'s next wipe comes from biweekly: 14 days after its last wipe. Sunday 1 November at 09:55 UTC is the date set for its next wipe. The world it runs now was created 38 days 11 hours. Its tags say it wipes every two weeks.
Player count
Where does Bandoler's 2x Trio | Living Wipe [Testing] sit among Rust servers?
Over the last seven days, Bandoler's 2x Trio | Living Wipe [Testing] has #14,352 for player hours, in the top – of all ranked servers.
What does the population on Bandoler's 2x Trio | Living Wipe [Testing] look like?
It has been 38 days 10 hours since Bandoler's 2x Trio | Living Wipe [Testing] was last seen, and it is offline right now.
Lists and filters
How should you read the tags on Bandoler's 2x Trio | Living Wipe [Testing]?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts3 (Group limit): Teams cap out at 3; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): The server wipes on a two-week cycle; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags Bandoler's 2x Trio | Living Wipe [Testing] publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Bandoler's 2x Trio | Living Wipe [Testing]?
Rust Server Score lists that include Bandoler's 2x Trio | Living Wipe [Testing]: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters 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.
Map and rules
How is Bandoler's 2x Trio | Living Wipe [Testing] set up, and what rules does it keep?
Bandoler's 2x Trio | Living Wipe [Testing] sets gather at 2x, as its name suggests. You can have up to 3 players in a group (trio). It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Bandoler's 2x Trio | Living Wipe [Testing] runs which map?
Bandoler's 2x Trio | Living Wipe [Testing] runs a procedural map, which the game generates.
Getting in
How do you get onto Bandoler's 2x Trio | Living Wipe [Testing]?
To connect, start Rust, press F1, and type client.connect 46.116.32.7:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^z,^y,^b,gmrust,cs164530,ts3
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts3
Group limitTeams cap out at 3.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework 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.
A term to build on.