Working its way up from the back of the class: #15,749 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
50/ 100
D
Holding steady: up 88 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 71% of all ranked servers, and #498 of the trio servers (top 86%). 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
Which region is 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV based in?
No region is published for 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 91.236.238.19:28015.
How dependable is 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV, and is it online at the moment?
You cannot join now: 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV is offline, last seen 34 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 24 September 2026.
On what Rust version does 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV sit?
The server 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV is on Rust network protocol 2633 and build 165217 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV reset?
2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 34 days 15 hours.
Player count
What position does 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV hold in the rankings?
Over the last seven days, 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV has #15,749 for player hours, in the top 71% of all ranked servers. In the trio group, it ranks #498.
What does the population on 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV look like?
The last sighting of 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV was 34 days 15 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): Its slot count is 10; ts3 (Group limit): No team may go above 3; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV 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.
Which Rust Server Score filters and lists feature 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV?
These Rust Server Score lists count 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV among them: 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 Carbon ^y; Group limit: Trio; Gather rate: 2x.
Map and rules
What settings and rules apply on 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV?
2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV sets gather at 2x, as its name suggests. The cap on group size is 3 players (trio). You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Which map is in play on 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV?
The game generates a procedural map for 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV.
Connecting
How do you get onto 2X | SOLO/DUO/TRIO | VANILLA+ | NO P2W | DEV?
Enter client.connect 91.236.238.19: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 asmp10,ptrak,$r?,v2633,gmrust,cs165217,ts3,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersIts slot count is 10.
ts3
Group limitNo team may go above 3.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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).