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 #531 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?
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 149.88.104.19:28015.
How reliable is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and is it up?
At this moment, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline; the last time it was seen was 10 days 10 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 19 September 2026.
What Rust version is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA on?
The server [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is on Rust network protocol 2631 and build 158240 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA wipe its map?
The record holds too few of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 91 days 21 hours.
Population
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit among Rust servers?
In the top 70% of all ranked servers, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sits at #15,275 for player hours over the last seven days. In the trio group, it ranks #531.
What does the population on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA look like?
It has been 10 days 10 hours since [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA was last seen, and it is offline right now.
Tags and filters
What do [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA's tags stand for?
You'll see [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; 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): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod) in the browser, which picks them up from the server. 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?
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.
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. The cap on group size is 3 players (trio). You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
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?
Enter client.connect 149.88.104.19:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
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 playersIts slot count is 50.
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
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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).