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 374 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
Which region is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA based in?
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 177.200.51.119:28015.
Is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA up, and how steady is its uptime?
At this moment, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA is offline; the last time it was seen was 39 days 12 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 19 September 2026.
On what Rust version does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA sit?
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.
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. The world it runs now was created 92 days 15 hours.
Player numbers
What position does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA hold in the rankings?
Over the last seven days, [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA has #15,508 for player hours, in the top – of all ranked servers.
Is [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA a busy server?
It has been 39 days 12 hours since [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA was last seen, and it is offline right now.
Tags
How should you read the tags on [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts3 (Group limit): No team may go above 3; v2631 (Protocol): To get in, your game needs to be on the same version: the protocol is 2631; cs158240 (Build): Build number: 158240; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here are the tags [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA publishes, and the game's server browser reads them. 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.
Where does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA appear in the Rust Server Score lists and filters?
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. 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.
Rules and settings
Which rules does [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA enforce, and what are its settings?
The name of [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA gives no gather rate. The cap on group size is 3 players (trio). It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA uses?
The game generates a procedural map for [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA.
Connecting
What is the way to join [BR/LATAM] COSTA MORTA | SOLO / DUO / TRIO | VANILLA?
Enter client.connect 177.200.51.119: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 limitNo team may go above 3.
v2631
ProtocolTo get in, your game needs to be on the same version: the protocol is 2631.
cs158240
BuildBuild number: 158240.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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.