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 331 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.
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
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. Rust Server Score takes the server's word for its location and does not trace the hardware. 103.139.178.224:28015 is the address to use.
How dependable is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA, and is it online at the moment?
You cannot join now: [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline, last seen 38 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 20 September 2026.
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. Steam updates your game for you, but you need the same protocol to join.
Resets
When does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA wipe, and how often?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 92 days 12 hours.
Player count
What position does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA hold in the rankings?
In the top – of all ranked servers, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sits at #15,465 for player hours over the last seven days.
Is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA a busy server?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline at the moment; the last time it was seen was 38 days 20 hours ago.
Tags
What is meant by 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): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; 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): RakNet handles it, the game's default network layer; $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?
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
Which rules does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA enforce, and what are its settings?
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). You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA uses?
[BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA runs a procedural map, which the game generates.
Getting in
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.224: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 modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts3
Group limitA team can hold 3 players at most.
v2631
ProtocolJoin only if your game runs protocol 2631.
cs158240
BuildBuild number: 158240.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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.