Working its way up from the back of the class: #16,590 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
48/ 100
D
Slipped a little: down 759 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.
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.
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. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
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
Wed 23 Sep, 22:55 UTC35d ago
0
–
running
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
EU · groups of 300+ · 2x · weekly · 313 on average
35 / 1000
Quick answers
from the figures on this page
About the server
Which region is 6_X2 based in?
You'll find no region listed by 6_X2. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 94.183.203.31:35200.
How reliable is 6_X2, and is it up?
You cannot join now: 6_X2 is offline, last seen 32 days 22 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 23 September 2026.
On what Rust version does 6_X2 sit?
Rust network protocol 2633 and build 165217 on Windows is what 6_X2 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does 6_X2 wipe its map?
The record holds too few of 6_X2's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 35 days 4 hours have passed since this world was made.
What happens on 6_X2 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Population
What position does 6_X2 hold in the rankings?
Over the last seven days, 6_X2 has #16,590 for player hours, in the top 71% of all ranked servers.
Is 6_X2 a busy server?
6_X2 is offline at the moment; the last time it was seen was 32 days 22 hours ago.
Tags
What is meant by the tags on 6_X2?
The game's browser takes its cue from the tags 6_X2 has set: gmrust (Game mode): Survival in the standard Rust style; mp650 (Max players): 650 slots are available; ts100 (Group limit): A team can hold 100 players at most; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. 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 6_X2?
Rust Server Score lists that include 6_X2: 2x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Server rules
How is 6_X2 set up, and what rules does it keep?
6_X2 sets gather at 2x, as its name suggests. The limit for a group is 100 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map 6_X2 uses?
A procedural map, generated by the game, is what 6_X2 runs.
Getting in
How should you connect to 6_X2?
To connect, start Rust, press F1, and type client.connect 94.183.203.31:35200. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp650,ptrak,$r?,v2633,gmrust,cs165217,ts100,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp650
Max players650 slots are available.
ts100
Group limitA team can hold 100 players at most.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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).