Working its way up from the back of the class: #15,977 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
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.
No daily history yet.
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 71% of all ranked servers, and #504 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
In what location does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit?
No region tag appears for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, but the name suggests South America. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 149.22.83.19:28015 is the address to use.
How dependable is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and is it online at the moment?
The server is down: [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline now, with the last sighting 20 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 7 October 2026, Rust Server Score saw it for the first time.
Which Rust version is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA running?
Rust network protocol 2631 and build 158240 on Windows is what [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA wipe, and how often?
The record holds too few of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 90 days 16 hours.
Player count
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit among Rust servers?
In the top 71% of all ranked servers, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sits at #15,977 for player hours over the last seven days. In the trio group, it ranks #504.
What does the population on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA look like?
It has been 20 days 20 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?
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): The server holds 50 slots; 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): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: 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 Rust Server Score filters and lists feature [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. You can find it under these server-list filters: Region: South America; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: Trio.
Server rules
How is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA set up, and what rules does it keep?
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). survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
The game generates a procedural map for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA.
Connecting
How should you connect to [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
Enter client.connect 149.22.83.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 modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts3
Group limitA team can hold 3 players at most.
v2631
ProtocolJoin only if your game runs protocol 2631.
cs158240
BuildBuild number: 158240.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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.