Working its way up from the back of the class: #15,945 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
53/ 100
D
Moving up: up 894 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.
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 #497 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
Which region is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA based in?
No region tag appears for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, but the name suggests South America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 146.70.198.253: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 23 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 6 October 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. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA wipe, and how often?
There are too few wipes on record for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 92 days 15 hours have passed since this world was made.
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,945 for player hours, in the top 71% of all ranked servers. In the trio group, it ranks #497.
How many players does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA usually have?
It has been 23 days 15 hours since [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA was last seen, and it is offline right now.
Tags
What do [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts3 (Group limit): Teams cap out at 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): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod) are the tags [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA publishes, and the game's server browser reads them. 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?
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. 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.
Server rules
How is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA set up, and what rules does it keep?
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). It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs which map?
The game generates a procedural map for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA.
How to join
How do you get onto [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
Enter client.connect 146.70.198.253: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 modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts3
Group limitTeams cap out at 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 codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is 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).