RUST METRICSFlight deck · live data
Data live Servers11,718 Players47,661 Populated3,204 Fresh wipes 3 h101 Scan5 min
‹ All servers198.89.99.196:28023
Online Full Queue Fresh wipe Wipe due No query

[BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10

Online SA 198.89.99.196:28023 checked 11m ago

2x trio weekly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Wed 23:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 58 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 55,674 ×1000

Entities

48 h range 46,288–56,091 · memory 1,932 MB
1239 ET SINCE RESTART 14:01

Uptime

14 h 1 min since its last restart, at the last reading
7-day average0peak 1
Rank#12,847top 58% · #197 in SA
Last wipe15d agoweekly schedule
Next wipe5d 20hTue 3 Nov, 20:59 UTC
Memory1,932MBat the last reading
REC 1

Players

AveragePeak
0123401:0010:0019:0004:0013:0023:00

Hourly average and peak, UTC.

REC 2

Server performance

02040608001:0010:0019:0004:0013:0023: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 10 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
15k10k15k20k10 Oct14 Oct17 Oct21 Oct24 Oct28 Oct

Top 58% of all ranked servers, top 82% in SA, and #484 of the trio servers (top 77%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Tuesday 3 November, 20:59 UTC, in 5d 20h. Its weekly schedule tag · low confidence

usual gap3.2 daysbetween real wipes
wipe-day peak15players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. WPT 1Tue 3 Nov, 20:59 UTC5d 20h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 18hFW
  3. WPT 3Tue 10 Nov, 20:59 UTC12d 20h
  4. WPT 4Tue 17 Nov, 20:59 UTC19d 20h
  5. WPT 5Tue 24 Nov, 20:59 UTC26d 20h
  6. WPT 6Tue 1 Dec, 20:59 UTC33d 20h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 18hFW
  8. WPT 8Tue 8 Dec, 20:59 UTC40d 20h

The first 48 hours of its last wipes

Tue 13 OctSat 10 Oct
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 16, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 20:59 UTC15d ago 16 – running 0
Sat 10 Oct, 15:58 UTC18d ago 14 halved by day 1 3.2 days 1

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 happens on [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 when wipe day comes?

At their busiest, its recent wipes drew 15 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.

How often does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 wipe, and when?

Its tag guides the prediction: too few of [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10's wipes are on record to confirm its schedule. Due on Tuesday 3 November at 20:59 UTC is its next wipe. The world it runs now was made 15 days 3 hours ago. The tags state a wipe schedule of one wipe a week.

Lists and filters

Which tags does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 carry, and what do they mean?

These are the tags [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^w (Weekly): It wipes each week; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game; SA (South America): The server browser files it under South America. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10: 2x Rust servers, checked live, Modded Rust servers, checked live and Trio servers, group limit 3. Reading: server list filters. It comes up under Region: South America; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Gather rate: 2x.

Population

What position does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 hold among Rust servers?

Player hours over the last seven days put [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 at #12,847, #197 in South America, in the top 58% of all ranked servers. Among servers in trio, it stands at #484.

How full does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 get?

Current headcount on [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 1.

Server

Which location does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 run from?

Reading: location. The SA tag puts [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 in South America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 198.89.99.196:28023.

What Rust version is [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 on?

Rust network protocol 2635 and build 168909 on Linux is the build [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 runs. Check: protocol. To join, your game must match; Steam handles the update.

How does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 perform?

Check: fps. Average 60 server fps over the last 48 hours, low of 58. Within range. Check: entities. The peak was 56,091, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 2,454 MB. Expect lag when fps falls and entities climb.

Is [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 up, and how often does it stay up?

Reading: online. [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 answers right now. Check: restart. The uptime it reports puts the last restart about 14 hours ago. Reading: 86% uptime over the last 7 full days. It was up 144 of 168 hours. The first sighting on Rust Metrics was 10 October 2026.

Settings and map

What rules does [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10 enforce, and what are its settings?

The name carries the rate: 2x gather on [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10. Check: group limit. 3 players, under the name trio. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Anti-cheat reading: VAC on, Valve's system.

Which map is live on [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10?

From seed 1337, the game generates the procedural map on [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10. Its size is 3,000. View it on RustMaps from this page: matching size and seed give an identical map. Read the map name: Wiped 15 days ago.

Connection

How do you connect to [BR/LATAM] Astro 2x | Solo/Duo/Trio | Wipe 13/10?

To join: start Rust, press F1 and type client.connect 198.89.99.196:28023. Or press Launch Rust here and Steam opens the game and connects you. https://discord.com/invite/C5YXxT3M35 is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^w,^v,SA,gmrust,cs168909,ts3,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts3
Group limit Teams are capped at 3.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly It wipes each week.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock game.

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.