Working its way up from the back of the class: #15,920 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
52/ 100
D
Moving up: up 619 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. 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
The region code for ANILCAN - SOLO 2X is ger, but no region is published. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 78.189.33.35:28015.
How reliable is ANILCAN - SOLO 2X, and is it up?
You cannot join now: ANILCAN - SOLO 2X is offline, last seen 26 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 2 October 2026.
What Rust version is ANILCAN - SOLO 2X on?
Rust network protocol 2617 and build 140534 on Windows is what ANILCAN - SOLO 2X runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does ANILCAN - SOLO 2X reset?
The record holds too few of ANILCAN - SOLO 2X'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. The world it runs now was created 26 days 17 hours.
Player numbers
Where does ANILCAN - SOLO 2X sit among Rust servers?
In the top 70% of all ranked servers, ANILCAN - SOLO 2X sits at #15,920 for player hours over the last seven days.
How many players does ANILCAN - SOLO 2X usually have?
It has been 26 days 16 hours since ANILCAN - SOLO 2X was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on ANILCAN - SOLO 2X?
You'll see ANILCAN - SOLO 2X tagged with gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2617 (Protocol): Join only if your game runs protocol 2617; cs140534 (Build): Build number: 140534; ptrak (Networking): RakNet handles it, the game's default network layer; $rger (Region code): It is filed under the region code ger 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.
Which Rust Server Score filters and lists feature ANILCAN - SOLO 2X?
These Rust Server Score lists count ANILCAN - SOLO 2X among them: 2x Rust servers, graded and Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
Map and rules
How is ANILCAN - SOLO 2X set up, and what rules does it keep?
ANILCAN - SOLO 2X sets gather at 2x, as its name suggests. The default of 8 players applies as the group cap. 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 under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on ANILCAN - SOLO 2X?
ANILCAN - SOLO 2X runs a procedural map, which the game generates.
Getting in
What is the way to join ANILCAN - SOLO 2X?
To connect, start Rust, press F1, and type client.connect 78.189.33.35:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$rger,v2617,gmrust,cs140534,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2617
ProtocolJoin only if your game runs protocol 2617.
cs140534
BuildBuild number: 140534.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rger
Region codeIt is filed under the region code ger.
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).