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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 393 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 70% 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, 17:33 UTC, in 2d 22h.
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?
The name of [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info points to Europe, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 64.188.73.189:28015 is the address to use.
How dependable is [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info, and is it online at the moment?
The server is down: [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info is offline now, with the last sighting 11 days ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 18 October 2026, Rust Server Score saw it for the first time.
What Rust version is [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info on?
Rust network protocol 2634 and build 167781 on Windows is what [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info reset?
weekly: 7 days after its last wipe gives the basis for estimating [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info's next wipe. Expect the next wipe on Sunday 1 November at 17:33 UTC. 11 days 1 hours have passed since this world was made. Its tags state that it wipes weekly.
Population
What position does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info hold in the rankings?
In the top 70% of all ranked servers, [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info sits at #15,255 for player hours over the last seven days. It comes #533 among servers in the trio group.
How many players does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info usually have?
[RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info is offline at the moment; the last time it was seen was 11 days ago.
Tags and filters
How should you read the tags on [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
The game's browser takes its cue from the tags [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info has set: gmrust (Game mode): Survival in the standard Rust style; mp150 (Max players): 150 slots are available; ts3 (Group limit): A team can hold 3 players at most; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^w (Weekly): It wipes weekly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
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. It shows under the following filters 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.
Map and rules
Which rules does [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info enforce, and what are its settings?
The name of [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info points to a 2x gather rate. You can have up to 3 players in a group (trio). You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. 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.
[RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info runs a procedural map, which the game generates.
How to join
What is the way to join [RU] 2X TRIO | Стаки 10000 | Макс. 3 | /info?
Enter client.connect 64.188.73.189: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 modeSurvival in the standard Rust style.
mp150
Max players150 slots are available.
ts3
Group limitA team can hold 3 players at most.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxidePlugin framework: 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).