Working its way up from the back of the class: #15,918 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
52/ 100
D
Moving up: up 621 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.
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
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
In what location does [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY sit?
You won't find a region tag on [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY, but its name indicates South America. Rust Server Score takes the server's word for its location and does not trace the hardware. 38.25.84.12:28015 is the address to use.
Is [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY up, and how steady is its uptime?
At this moment, [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY is offline; the last time it was seen was 27 days 18 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 2 October 2026, Rust Server Score saw it for the first time.
What Rust version is [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY on?
Rust network protocol 2634 and build 166494 on Linux is what [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY reset?
The record holds too few of [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY's wipes to tell 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 27 days 18 hours.
Population
What position does [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY hold in the rankings?
In the top 69% of all ranked servers, [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY sits at #15,918 for player hours over the last seven days.
Is [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY a busy server?
[PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY is offline at the moment; the last time it was seen was 27 days 18 hours ago.
Tags
How should you read the tags on [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY?
You'll see [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 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; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY: 2x Rust servers, graded and Best community servers, graded. It shows under the following filters on the server list: Region: South America; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
Server rules
What settings and rules apply on [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY?
Going by its name, [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY runs 2x gather. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY?
The game generates a procedural map for [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY.
Connecting
How should you connect to [PE/LATAM] APEX 2X | SOLO/DUO/TRIO | WIPED TODAY?
To connect, start Rust, press F1, and type client.connect 38.25.84.12:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166494,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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. Strongest in momentum (D); standing is the one to work on (F).