Working its way up from the back of the class: #15,275 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
51/ 100
D
Moving up: up 373 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.
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 70% of all ranked servers, and #530 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
Where in the world is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
The name of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA points to South America, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 177.200.62.201: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 10 days 15 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 8 October 2026.
Which Rust version is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA running?
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.
Wipe cycle
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 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 #15,275 for player hours, in the top 70% of all ranked servers. In the trio group, it ranks #530.
How many players does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA usually have?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline at the moment; the last time it was seen was 10 days 15 hours ago.
Tags and filters
What is meant by the tags on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts3 (Group limit): No team may go above 3; v2631 (Protocol): The game protocol is 2631, so your game must match that version to join; cs158240 (Build): Build number: 158240; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod) are the tags [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the 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. 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.
Rules and settings
What settings and rules apply on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
You will find no gather rate in the name of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA. 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. The server browser lists it under Community, as a community server. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
A procedural map, generated by the game, is what [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs.
How to join
What is the way to join [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
To connect, start Rust, press F1, and type client.connect 177.200.62.201: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 limitNo team may go above 3.
v2631
ProtocolThe game protocol is 2631, so your game must match that version to join.
cs158240
BuildBuild number: 158240.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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).