Offline 177.200.51.150:28015 checked 44d ago
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA
Connect
srv = rust.server("177.200.51.150:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestWipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 177.200.51.150:28015
- region
- –
- max players
- 50
- group limit
- trio
- wipe schedule
- –
- last wipe
- 29 Jul 2026, 04:54 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [BR/LATAM] TERRA HOSTIL VANILLA | SOLO/ DUO/ TRIO | | SA · trio · weekly · 28 on average | 21/250 |
| 1 | [LATAM] Rustako Solo/Duo/Trio | Survival | FULLWIPE 22/10 19hs | SA · trio · biweekly · 23 on average | 0/165 |
| 2 | [LATAM] SOLO NOOB Solo/Duo/Trio | 26/10 Wipe | SA · trio · weekly · 8 on average | 4/200 |
| 3 | Brasa.gg - BR Vanilla Solo/Duo/Trio | SA · trio · 4 on average | 2/100 |
| 4 | [LATAM] DISTRITO CERO | VANILLA | SOLO/DUO/TRIO | HOY 14:00 | SA · trio · 3 on average | 0/100 |
| 5 | La Taberna [LATAM] | Solo/Duo/Trio | Full Wipe 25/10 | SA · trio · 2 on average | 4/100 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA rank?
Player hours over seven days put [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA at #15,025, in the top – of the ranked set.
How full does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA run?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA returns no live count at this refresh, having last been seen 44 days 22 hours ago.
Server facts
What Rust version does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA run?
The build is Rust network protocol 2631 and build 158240 on Windows, run by [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA. Steam updates your game for you, but the protocol must match to join.
Is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA up, and what does its uptime show?
Offline now for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, last seen 44 days 22 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit?
Its name points to South America, but [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA publishes no region tag. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 177.200.51.150:28015.
Settings and map
What rules and settings are recorded for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
You will not find a gather rate in the string [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA. trio sets the cap: 3 players per group. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Community is its browser category. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
The game generates its map: procedural, on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA.
Wipe data
On what schedule does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA wipe?
The record for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 92 days 10 hours ago.
Lists and tags
Which lists on Rust Data hold [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and which filters?
These Rust Data lists include [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA: Rust community servers, unfiltered and Trio Rust servers. It appears under these filters on the server list: Region: South America; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Trio.
How should you read the server tags on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
The game's server browser reads these tags from [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts3 (Group limit): No team may exceed 3; v2631 (Protocol): The server speaks protocol 2631, so match your game version; cs158240 (Build): Recorded game build: 158240; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
In Rust, F1 opens the console: type client.connect 177.200.51.150:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.