RUST METRICSFlight deck · live data
Data live Servers11,859 Players101,852 Populated3,917 Fresh wipes 3 h538 Scan5 min
‹ All servers143.20.0.213:28015
Online Full Queue Fresh wipe Wipe due No query

[BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY

Online SA 143.20.0.213:28015 checked 8m ago

2x trio weekly wipes moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 18:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 20 SERVER FPS

Server fps

48 h low 12 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 48,129 ×1000

Entities

48 h range 47,868–50,434 · memory 2,453 MB
1239 ET SINCE RESTART 4D 14H

Uptime

4 days 14 hours since its last restart, at the last reading
7-day average0peak 1
Rank#9,232top 41% · #176 in SA
Last wipe51m agoweekly schedule
Next wipe6d 22hThu 5 Nov, 19:00 UTC FW
Memory2,453MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75121:0006:0015:0000:0009:0018:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304021:0006:0015:0000:0009:0018:00

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 41% of all ranked servers, top 74% in SA, and #440 of the trio servers (top 70%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. The force wipe · high confidence

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 22hFW
  2. WPT 2Thu 12 Nov, 19:12 UTC13d 23h
  3. WPT 3Thu 19 Nov, 19:12 UTC20d 23h
  4. WPT 4Thu 26 Nov, 19:12 UTC27d 23h
  5. WPT 5Thu 3 Dec, 19:00 UTC34d 22hFW
  6. WPT 6Thu 10 Dec, 19:12 UTC41d 23h
LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 19:12 UTC51m ago – – running 0

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

Wipe timing

When does [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY wipe?

Its tag guides the prediction: too few of [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY's wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 51 minutes ago the current world was made. Its tags carry a weekly wipe schedule.

Lists and filters

How should you read the tags on [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^w (Weekly): It wipes each week; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon; SA (South America): The server browser files it under South America from [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY appear in Rust Metrics lists and filters?

These Rust Metrics lists carry [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. Check: filters. On the server list it appears under these: Region: South America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 24 hours; Gather rate: 2x.

Occupancy

What position does [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY hold among Rust servers?

Player hours over the last seven days put [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY at #9,232, #176 in South America, in the top 41% of all ranked servers. Among servers in trio, it stands at #440.

What player count does [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY carry?

0 of 50 slots are filled on [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 22:00 UTC, averaging 1 players at that hour.

Operator and location

What location is [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY hosted in?

Its SA tag places [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY in South America. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 143.20.0.213:28015.

What Rust version is [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY on?

Rust network protocol 2635 and build 168909 on Linux is the build [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY runs. Matching protocol is required to join. Let Steam update your game.

Is performance on [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY within range?

Check: fps. Average 24 server fps over the last 48 hours, low of 12. Within range. Check: entities. The peak was 50,434, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,028 MB. Lag, as players feel it, is low fps plus a climbing entity count.

Is [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY up, and how often does it stay up?

Check: connection. [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY is online at this moment. Check: restart. The uptime it reports puts the last restart about 4 days 14 hours ago. Reading: 99% uptime over the last 4 full days. It was up 95 of 96 hours. The first sighting on Rust Metrics was 24 October 2026.

Map and rules

What rules does [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY enforce, and what are its settings?

Gather rate check: 2x. That comes from the name [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY. Groups stop at 3 players. The label given is trio. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY on?

From seed 270747, the game generates the procedural map on [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY. Its size is 3,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to [BR] RUST 2X | SOLO/DUO/TRIO | WEEKLY?

To join: start Rust, press F1 and type client.connect 143.20.0.213:28015. Or press Launch Rust here and Steam opens the game and connects you. https://app.bluewave.host/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^z,^y,^w,SA,gmrust,cs168909,ts3

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts3
Group limit Teams are capped at 3.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly It wipes each week.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Plugin framework in use: Carbon.

Region

SA
South America The server browser files it under South America.

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.