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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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 RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots based in?
No region tag appears for RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots, 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. You can connect at 34.176.47.222:28015.
Is RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots up, and how steady is its uptime?
The server is down: RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots is offline now, with the last sighting 44 days 15 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots running?
You will find RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots on Rust network protocol 2632 and build 161125, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots wipe its map?
RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 62 days 17 hours.
Player numbers
Where does RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots place in the wider field of Rust servers?
Over the last seven days, RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots has #15,078 for player hours, in the top – of all ranked servers.
How many players does RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots usually have?
The last sighting of RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots was 44 days 15 hours ago, and it is offline right now.
Tags
What is meant by the tags on RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): 200 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs161125 (Build): The game build is 161125; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots 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.
Which Rust Server Score filters and lists feature RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots?
These Rust Server Score lists count RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots among them: Modded Rust servers, graded. It shows under the following filters on the server list: Region: South America; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 1x.
Rules and settings
What settings and rules apply on RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots?
Going by its name, RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots runs 1x gather. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. The server runs Valve's anti-cheat, VAC.
RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots runs which map?
The game generates a procedural map for RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots.
How to join
What is the way to join RustLatam | Vanilla x1 | Solo | LATAM | 200 Slots?
To connect, start Rust, press F1, and type client.connect 34.176.47.222:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2632,gmrust,cs161125,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max players200 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs161125
BuildThe game build is 161125.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.
Not enough figures yet to write a report. Check back after a few days on the list.