Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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 takes the server's word for its location and does not trace the hardware. 177.200.51.150:28015 is the address to use.
How dependable is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and is it online at the moment?
You cannot join now: [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline, last seen 44 days 19 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA on?
Rust network protocol 2631 and build 158240 on Windows is what [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA reset?
The record holds too few of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 92 days 7 hours.
Population
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit among Rust servers?
In the top – of all ranked servers, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sits at #15,025 for player hours over the last seven days.
Is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA a busy server?
The last sighting of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA was 44 days 19 hours ago, and it is offline right now.
Lists and filters
How should you read the tags on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
You'll see [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts3 (Group limit): No team may go above 3; v2631 (Protocol): To get in, your game needs to be on the same version: the protocol is 2631; cs158240 (Build): This runs on build 158240; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA appear in the Rust Server Score lists and filters?
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.
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. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs which map?
A procedural map, generated by the game, is what [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs.
Getting in
How do you get onto [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
To connect, start Rust, press F1, and type client.connect 177.200.51.150: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 modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts3
Group limitNo team may go above 3.
v2631
ProtocolTo get in, your game needs to be on the same version: the protocol is 2631.
cs158240
BuildThis runs on build 158240.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
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.
Not enough figures yet to write a report. Check back after a few days on the list.