Working its way up from the back of the class: #15,255 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
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 722 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.
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 18 Sep. 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, top 90% in SA. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W···W·
··WW···
·W··W··
·W·····
·W·····
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Tuesday 3 November, 21:06 UTC, in 6d 11h.
Its weekly schedule tag · low confidence
usual gap3.6 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak0players, last three wipes
crowd held50%else halves by day 4
Coming wipes
6d 11hTue 3 Nov, 21:06 UTC
8d 9hThu 5 Nov, 19:00 UTCFW
13d 11hTue 10 Nov, 21:06 UTC
20d 11hTue 17 Nov, 21:06 UTC
27d 11hTue 24 Nov, 21:06 UTC
34d 11hTue 1 Dec, 21:06 UTC
36d 9hThu 3 Dec, 19:00 UTCFW
41d 11hTue 8 Dec, 21:06 UTC
The first 48 hours of its last wipes
Tue 13 OctTue 6 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 13 Oct, 21:06 UTC14d ago
0
–
running
0
Tue 6 Oct, 21:05 UTC21d ago
0
–
7 days
0
Fri 2 Oct, 21:05 UTC25d ago
0
–
4 days
0
Fri 2 Oct, 00:12 UTC26d ago
1
–
0.9 days
0
Tue 29 Sep, 21:07 UTC28d ago
2
✓ held half
2.1 days
0
Thu 24 Sep, 03:32 UTC34d ago
1
halved by day 4
5.7 days
1
Wed 23 Sep, 14:06 UTC34d ago
1
–
0.6 days
0
Sat 19 Sep, 00:13 UTC39d ago
1
halved by day 2
4.6 days
0
Tue 15 Sep, 20:33 UTC42d ago
1
✓ held half
3.2 days
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
In what location does [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 sit?
You'll see [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 listed in South America, tagged SA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 45.182.149.207:28015 is the address to use.
Is [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 up, and how steady is its uptime?
The server is down: [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 is offline now, with the last sighting 14 days 10 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 15 September 2026, Rust Server Score saw it for the first time.
On what Rust version does [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 sit?
The server [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 is on Rust network protocol 2634 and build 167781 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 wipe, and how often?
Its tag sets the prediction, as the record holds too few of [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10's wipes to confirm its schedule. Expect the next wipe on Tuesday 3 November at 21:06 UTC. 14 days 11 hours have passed since this world was made. Its tags state that it wipes weekly.
What happens on [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 50% of its recent wipes. In the other wipes it slipped under half by day 4.
Player numbers
Where does [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 place in the wider field of Rust servers?
In South America, [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 is #201, and overall it is #15,255 on player hours over the last seven days, in the top 71% of all ranked servers.
What does the population on [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 look like?
[BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 is offline at the moment; the last time it was seen was 14 days 10 hours ago.
Lists and filters
What do [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^o (Oxide): Plugin framework: Oxide (uMod); SA (South America): In the server browser it appears under South America are the tags [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 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] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 among them: 2x Rust servers, graded and Best community servers, graded. These filters bring it up on the server list: Region: South America; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.
Server rules
What settings and rules apply on [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10?
[BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 uses?
A procedural map of size 3,300 and seed 1627330267, generated by the game, is what [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join [BR/LATAM] RAVAGE 2X | SOLO/DUO/TRIO/QUAD | WIPE 13/10?
To connect, start Rust, press F1, and type client.connect 45.182.149.207:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,SA,gmrust,cs167781,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
SA
South AmericaIn the server browser it appears under South America.
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).