Working its way up from the back of the class: #15,704 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
27/ 100
F
Lost ground: down 7,301 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
AveragePeakWipe
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 3 Oct. 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. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 12:22 UTC26d ago
3
–
running
0
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 [Octagrama] Latam X5: TEAM 8 based in?
No region tag appears for [Octagrama] Latam X5: TEAM 8, 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 108.181.101.18:28016.
How reliable is [Octagrama] Latam X5: TEAM 8, and is it up?
The server is down: [Octagrama] Latam X5: TEAM 8 is offline now, with the last sighting 21 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 3 October 2026.
Which Rust version is [Octagrama] Latam X5: TEAM 8 running?
The server [Octagrama] Latam X5: TEAM 8 is on Rust network protocol 2634 and build 166652 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does [Octagrama] Latam X5: TEAM 8 wipe its map?
[Octagrama] Latam X5: TEAM 8 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. The world it runs now was created 26 days 2 hours.
What should you expect from wipe day on [Octagrama] Latam X5: TEAM 8?
The average peak on its recent wipes was 3 players. 5 hours after the latest wipe began, the crowd hit its peak.
Population
What position does [Octagrama] Latam X5: TEAM 8 hold in the rankings?
Over the last seven days, [Octagrama] Latam X5: TEAM 8 has #15,704 for player hours, in the top 71% of all ranked servers.
What does the population on [Octagrama] Latam X5: TEAM 8 look like?
It has been 21 days 11 hours since [Octagrama] Latam X5: TEAM 8 was last seen, and it is offline right now.
Tags
What do [Octagrama] Latam X5: TEAM 8's tags stand for?
You'll see [Octagrama] Latam X5: TEAM 8 tagged with gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): 150 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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.
Where does [Octagrama] Latam X5: TEAM 8 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [Octagrama] Latam X5: TEAM 8 among them: 5x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: South America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
Rules and settings
Which rules does [Octagrama] Latam X5: TEAM 8 enforce, and what are its settings?
[Octagrama] Latam X5: TEAM 8 sets gather at 5x, as its name suggests. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
[Octagrama] Latam X5: TEAM 8 runs which map?
The game generates the procedural map on [Octagrama] Latam X5: TEAM 8 at size 3,000 with seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How should you connect to [Octagrama] Latam X5: TEAM 8?
To connect, start Rust, press F1, and type client.connect 108.181.101.18:28016. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://www.gamehost.cl/.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp150
Max players150 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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. Even marks across the subjects, from F to F.