Working its way up from the back of the class: #16,019 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
50/ 100
D
Holding steady: up 92 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 69% of all ranked servers, and #493 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA based in?
You won't find a region tag on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, but its name indicates South America. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 177.200.51.51:28015.
How reliable is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and is it up?
The server is down: [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline now, with the last sighting 27 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 21 September 2026.
On what Rust version does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit?
You will find [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA on Rust network protocol 2631 and build 158240, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA wipe its map?
There are too few wipes on record for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 92 days 15 hours have passed since this world was made.
Player numbers
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA place in the wider field of Rust servers?
Over the last seven days, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA has #16,019 for player hours, in the top 69% of all ranked servers. It comes #493 among servers in the trio group.
What does the population on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA look like?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline at the moment; the last time it was seen was 27 days 23 hours ago.
Tags and filters
What do [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA's tags stand for?
The game's browser takes its cue from the tags [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts3 (Group limit): A team can hold 3 players at most; v2631 (Protocol): Join only if your game runs protocol 2631; cs158240 (Build): This runs on build 158240; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod). Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
Rust Server Score lists that include [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA: Best community servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Region: South America; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Trio.
Map and rules
What settings and rules apply on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
The name of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA gives no gather rate. You can have up to 3 players in a group (trio). It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs a procedural map, which the game generates.
How to join
How should you connect to [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
To connect, start Rust, press F1, and type client.connect 177.200.51.51:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2631,gmrust,cs158240,ts3,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts3
Group limitA team can hold 3 players at most.
v2631
ProtocolJoin only if your game runs protocol 2631.
cs158240
BuildThis runs on build 158240.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).