Station XX-13777 · no signal
#Brasa2x
Offline 138.121.65.28:28015 checked 22d ago
- Players now
- 1/ 100
- 1% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,777
- top 61%
- Last wipe
- 24d ago
- monthly schedule
- Next wipe
- 7d 21h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 100 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence
- usual gap
- 0.8 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 7d 21hThu 5 Nov, 19:00 UTCFW
- 35d 21hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 4 Oct, 21:16 UTC24d ago | M0.0■steady | 1 | – | running | 1 | |
| Sun 4 Oct, 01:01 UTC24d ago | M0.0■steady | 1 | – | 0.8 days | 1 |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on #Brasa2x?
The map on #Brasa2x is procedural, produced by the game.
Which settings and rules apply on #Brasa2x?
You will find no gather rate in the name of #Brasa2x. At the game's default, groups can have up to 8 players. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on #Brasa2x right now?
#Brasa2x is not responding at this moment and is offline, last seen 22 days 20 hours ago.
How does #Brasa2x rank against other Rust servers?
On player hours for the past week, #Brasa2x sits at #13,777, which puts it inside the top 61% of every ranked server.
Server facts
How reliably does #Brasa2x stay online?
As recorded now, #Brasa2x is not reachable, the last contact having been 22 days 20 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 3 October 2026 is when Rust Server Trends first recorded it.
Which region does #Brasa2x run from?
No region is published by #Brasa2x. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 138.121.65.28:28015 is the address it uses.
Which Rust version is #Brasa2x running?
#Brasa2x is running Rust network protocol 2634 and build 166652 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on #Brasa2x?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does #Brasa2x wipe, and on which days?
At the force wipe each month #Brasa2x wipes, and at no other time. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 24 days is how long the current world has been running. The tags it publishes carry a monthly wipe schedule.
Lists and tags
What do the server tags on #Brasa2x mean?
The game's server browser reads the tags #Brasa2x publishes: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does #Brasa2x appear?
You will find #Brasa2x on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How to join
What steps get you onto #Brasa2x?
Enter client.connect 138.121.65.28:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.