Working its way up from the back of the class: #15,478 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
49/ 100
D
Slipped a little: down 232 places this week. Nothing a good wipe can't fix.
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.
AveragePeak
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 68% of all ranked servers, and #497 of the trio servers (top 81%). 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
In what location does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit?
You won't find a region tag on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, but its name indicates South America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 177.200.51.36:28015.
How dependable is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and is it online at the moment?
At this moment, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline; the last time it was seen was 37 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
Which Rust version is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA running?
The server [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is on Rust network protocol 2631 and build 158240 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA reset?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 91 days 17 hours.
Population
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 #15,478 for player hours, in the top 68% of all ranked servers. It comes #497 among servers in the trio group.
What does the population on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA look like?
It has been 37 days 14 hours since [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
The game's browser takes its cue from the tags [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA has set: gmrust (Game mode): Survival in the standard Rust style; 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): Build number: 158240; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod). The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
These Rust Server Score lists count [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA among them: Best community servers, graded and Rust servers with a trio group limit. It shows under the following 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.
Rules and settings
What settings and rules apply on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
Nothing in the name of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA states a gather rate. The cap on group size is 3 players (trio). You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA uses?
A procedural map, generated by the game, is what [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs.
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.36: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 modeSurvival in the standard Rust style.
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
BuildBuild number: 158240.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: 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).