Rust Server TrendsSeismic network · station log
Recording Stations11,866 Players94,541 Active3,878 Wipes · 3 h396 48 h

Station SA-15961 · no signal

[BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09

Offline SA 169.155.127.10:28015 checked 24d ago

biweekly wipes vanillamoddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,961
top 71% · #210 in SA
Last wipe
28d ago
biweekly schedule
Next wipe
7d 3h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station SA-15961 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 100 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep28 Sep3 Oct7 Oct11 Oct

Top 71% of all ranked servers, top 89% in SA. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

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

usual gap
1 daysbetween real wipes
wipe-day peak
4players, last three wipes

Coming wipes

  1. 7d 3hThu 5 Nov, 19:00 UTCFW
  2. 13d 6hWed 11 Nov, 22:39 UTC
  3. 27d 6hWed 25 Nov, 22:39 UTC
  4. 35d 3hThu 3 Dec, 19:00 UTCFW
  5. 41d 6hWed 9 Dec, 22:39 UTC

The first 48 hours of its last wipes

Wed 30 SepTue 29 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 30 Sep, 22:39 UTC28d ago M0.0rising 1 – running 0
Tue 29 Sep, 22:08 UTC29d ago M0.8rising 7 – 1 days 0

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[LATAM] www.pandarust.ar Vanilla | WIPE 22/10 17hs SA · groups of 5 · biweekly · 60 on average
10/ 200
[LATAM] LUNARUST Vanilla | 27/10 Wipe SA · groups of 5 · weekly · 18 on average
10/ 200
[LATAM] RUSTICO Vanilla | WIPE 26/10 SA · groups of 5 · weekly · 5 on average
3/ 300
EL MATADERO SA · quad · biweekly · 2 on average
1/ 50
[LATAM] Vicio Sudamerica Rust SA · groups of 8+ · biweekly · 1 on average
3/ 100
Brasa.gg - BR 2X SA · groups of 6 · 2x · weekly · 115 on average
18/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09?

[BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 runs a procedural map of size 3,800 with seed 1, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. Its map carries the name Custom Map.

Which settings and rules apply on [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09?

The name of [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 gives no gather rate. The group limit is 5 players. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. By its own description it is vanilla: no changed rates, kits or rules: this is the game as Facepunch ships it. The server has VAC on, Valve's anti-cheat.

Live population

What is the current population on [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09?

[BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 is not responding at this moment and is offline, last seen 24 days 17 hours ago.

How does [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 rank against other Rust servers?

[BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 is #210 in South America and #15,961 worldwide on the past week's player hours, within the top 71% of ranked servers.

Operator and location

How reliably does [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 stay online?

As recorded now, [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 is not reachable, the last contact having been 24 days 17 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 run from?

The SA tag is how [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 lists itself in South America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 169.155.127.10:28015.

Which Rust version is [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 running?

On Linux, [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 runs Rust network protocol 2633 and build 165217. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09?

4 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.

How often does [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 wipe, and on which days?

The prediction is taken from its tag, since [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 has too few wipes on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 28 days 16 hours. In its tags it sets out a wipe schedule of every two weeks.

Server tags

What do the server tags on [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 mean?

Tags published by [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts5 (Group limit): Teams are capped at 5 players; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): Game build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; SA (South America): South America is the region it's listed under in the browser. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 appear?

You will find [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09 on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: South America; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Join the server

What steps get you onto [BR/LATAM] GigA World | Solo - Squad Max 5 | FULLWIPE 29.09?

You can connect by pressing F1 in Rust and typing client.connect 169.155.127.10:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^b,^v,SA,gmrust,cs165217,ts5,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players 100 slots are available.
ts5
Group limit Teams are capped at 5 players.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build Game build: 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla No changed rates, kits or rules: this is the game as Facepunch ships it.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Region

SA
South America South America is the region it's listed under in the browser.

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.

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.