Working its way up from the back of the class: #15,247 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
51/ 100
D
Moving up: up 401 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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 18 Oct. 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, and #533 of the trio servers (top 85%). 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
Next wipe Sunday 1 November, 18:21 UTC, in 3d 12h.
Weekly: 7 days after its last 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
Where in the world is [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
No region tag appears for [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info, but the name suggests Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 171.22.130.49:28015 is the address to use.
How reliable is [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info, and is it up?
The server is down: [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info is offline now, with the last sighting 10 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 18 October 2026, Rust Server Score saw it for the first time.
Which Rust version is [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info running?
Rust network protocol 2634 and build 167781 on Windows is what [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info reset?
The estimate for [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info's next wipe comes from weekly: 7 days after its last wipe. Expect the next wipe on Sunday 1 November at 18:21 UTC. It has been running its current world for 10 days 11 hours. Wipes are scheduled weekly, according to its tags.
Player count
Where does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info place in the wider field of Rust servers?
In the top 69% of all ranked servers, [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info sits at #15,247 for player hours over the last seven days. In the trio group, it ranks #533.
How many players does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info usually have?
It has been 10 days 9 hours since [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): 150 slots are available; ts3 (Group limit): Teams cap out at 3; 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): No region code has been set; ^w (Weekly): Wipes come once a week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info publishes, and the game's server browser reads them. 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 [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info among them: 2x Rust servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Rules and settings
What settings and rules apply on [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
The name of [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info points to a 2x gather rate. The cap on group size is 3 players (trio). It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info uses?
A procedural map of size 3,500 and seed 879905954, generated by the game, is what [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
How should you connect to [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
Enter client.connect 171.22.130.49:28015 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 asmp150,ptrak,$r?,v2634,^w,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp150
Max players150 slots are available.
ts3
Group limitTeams cap out at 3.
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 codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Strongest in momentum (D); standing is the one to work on (F).