Working its way up from the back of the class: #16,608 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
49/ 100
D
Slipped a little: down 497 places this week. Nothing a good wipe can't fix.
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 #492 of the trio servers (top 84%). 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 CAIRNWIRE | 2x Vanilla+ | Trio | Monthly sit?
You'll find no region listed by CAIRNWIRE | 2x Vanilla+ | Trio | Monthly. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 89.187.179.29:28015 is the address to use.
Is CAIRNWIRE | 2x Vanilla+ | Trio | Monthly up, and how steady is its uptime?
The server is down: CAIRNWIRE | 2x Vanilla+ | Trio | Monthly is offline now, with the last sighting 27 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
On what Rust version does CAIRNWIRE | 2x Vanilla+ | Trio | Monthly sit?
Rust network protocol 2633 and build 165217 on Windows is what CAIRNWIRE | 2x Vanilla+ | Trio | Monthly runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does CAIRNWIRE | 2x Vanilla+ | Trio | Monthly wipe, and how often?
The record holds too few of CAIRNWIRE | 2x Vanilla+ | Trio | Monthly's wipes to tell 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 27 days 20 hours.
Player count
Where does CAIRNWIRE | 2x Vanilla+ | Trio | Monthly place in the wider field of Rust servers?
Over the last seven days, CAIRNWIRE | 2x Vanilla+ | Trio | Monthly has #16,608 for player hours, in the top 70% of all ranked servers. In the trio group, it ranks #492.
What does the population on CAIRNWIRE | 2x Vanilla+ | Trio | Monthly look like?
The last sighting of CAIRNWIRE | 2x Vanilla+ | Trio | Monthly was 27 days 20 hours ago, and it is offline right now.
Tags
How should you read the tags on CAIRNWIRE | 2x Vanilla+ | Trio | Monthly?
You'll see CAIRNWIRE | 2x Vanilla+ | Trio | Monthly tagged with gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): The server holds 5 slots; ts3 (Group limit): Teams cap out at 3; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. 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 CAIRNWIRE | 2x Vanilla+ | Trio | Monthly appear in the Rust Server Score lists and filters?
Rust Server Score lists that include CAIRNWIRE | 2x Vanilla+ | Trio | Monthly: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Gather rate: 2x.
Map and rules
What settings and rules apply on CAIRNWIRE | 2x Vanilla+ | Trio | Monthly?
CAIRNWIRE | 2x Vanilla+ | Trio | Monthly sets gather at 2x, as its name suggests. You can have up to 3 players in a group (trio). survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on CAIRNWIRE | 2x Vanilla+ | Trio | Monthly?
A procedural map, generated by the game, is what CAIRNWIRE | 2x Vanilla+ | Trio | Monthly runs.
Connecting
How do you get onto CAIRNWIRE | 2x Vanilla+ | Trio | Monthly?
To connect, start Rust, press F1, and type client.connect 89.187.179.29:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs165217,ts3,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp5
Max playersThe server holds 5 slots.
ts3
Group limitTeams cap out at 3.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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).