Working its way up from the back of the class: #16,084 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
50/ 100
D
Holding steady: up 27 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (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.
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
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
EU · groups of 100+ · 1000x · weekly · 61 on average
95 / 95
Quick answers
from the figures on this page
Server details
In what location does LatamGS Staging - Battlefield sit?
LatamGS Staging - Battlefield leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 179.238.35.104:28135 is the address to use.
How reliable is LatamGS Staging - Battlefield, and is it up?
You cannot join now: LatamGS Staging - Battlefield is offline, last seen 27 days 15 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 30 September 2026.
What Rust version is LatamGS Staging - Battlefield on?
Rust network protocol 2634 and build 166493 on Linux is what LatamGS Staging - Battlefield runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does LatamGS Staging - Battlefield reset?
LatamGS Staging - Battlefield has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 28 days 11 hours.
Player count
Where does LatamGS Staging - Battlefield sit among Rust servers?
Over the last seven days, LatamGS Staging - Battlefield has #16,084 for player hours, in the top 69% of all ranked servers.
How many players does LatamGS Staging - Battlefield usually have?
The last sighting of LatamGS Staging - Battlefield was 27 days 15 hours ago, and it is offline right now.
Tags
How should you read the tags on LatamGS Staging - Battlefield?
The game's browser takes its cue from the tags LatamGS Staging - Battlefield has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166493 (Build): This runs on build 166493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; rustmaps (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. 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 LatamGS Staging - Battlefield?
These Rust Server Score lists count LatamGS Staging - Battlefield among them: Modded Rust servers, graded and Rust battlefield servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
How is LatamGS Staging - Battlefield set up, and what rules does it keep?
Nothing in the name of LatamGS Staging - Battlefield states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, 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.
Connecting
How should you connect to LatamGS Staging - Battlefield?
Enter client.connect 179.238.35.104:28135 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 asmp100,ptrak,$r?,v2634,gmrust,cs166493,ts8,^o^z,rustmaps,modded
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166493
BuildThis runs on build 166493.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
rustmaps
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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. Strongest in momentum (D); standing is the one to work on (F).