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
49/ 100
D
Slipped a little: down 346 places this week. Nothing a good wipe can't fix.
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.
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
In what location does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit?
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 103.139.178.159:28015.
Is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA up, and how steady is its uptime?
You cannot join now: [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline, last seen 38 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 19 September 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. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA reset?
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 1 hours 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,480 for player hours, in the top – of all ranked servers.
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 38 days 12 hours ago, and it is offline right now.
Tags
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): 50 slots are available; ts3 (Group limit): Teams cap out at 3; 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): 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. 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?
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
What settings and rules apply on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
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, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
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?
To connect, start Rust, press F1, and type client.connect 103.139.178.159: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 players50 slots are available.
ts3
Group limitTeams cap out at 3.
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 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.
A term to build on.