ANILCAN - SOLO 2X
Offline 78.189.33.35:28015 checked 15d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes
- 20/ 100
- 2/ 100
- 2/ 200
- 6/ 100
- 1/ 200
- 3/ 60
Quick answers
Tags and search
Where does ANILCAN - SOLO 2X appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry ANILCAN - SOLO 2X are: 2x Rust servers and Rust community servers, going deep. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 2x.
What's the meaning of the tags on ANILCAN - SOLO 2X?
The server browser shows these tags for ANILCAN - SOLO 2X: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies here; v2617 (Protocol): This server runs game protocol 2617, so your game must match that version to join; cs140534 (Build): The build number is 140534; ptrak (Networking): RakNet, the network layer Rust uses by default; $rger (Region code): Region: ger. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
Where can you find ANILCAN - SOLO 2X?
No region is published by ANILCAN - SOLO 2X, and the region code is ger. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 78.189.33.35:28015.
How reliable is ANILCAN - SOLO 2X?
ANILCAN - SOLO 2X is down at the moment; it was last up 15 days 17 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 2 October 2026 is when Rust Going Deep first saw it.
What Rust version is ANILCAN - SOLO 2X on?
Rust network protocol 2617 and build 140534 is what ANILCAN - SOLO 2X runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does ANILCAN - SOLO 2X wipe?
Too few wipes are on record for ANILCAN - SOLO 2X to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 15 days 19 hours is how long ago this world came into being.
Map and rules
What settings and rules have been applied to ANILCAN - SOLO 2X?
The name says it: ANILCAN - SOLO 2X is a 2x gather server. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. Community is where the server browser puts it, as a community server. VAC is on: Valve's anti-cheat is active.
Which map is active on ANILCAN - SOLO 2X?
A procedural map, generated by the game, is in play on ANILCAN - SOLO 2X.
Player count
How many players are on ANILCAN - SOLO 2X?
ANILCAN - SOLO 2X was last seen 15 days 17 hours ago and is offline as you read this.
What position does ANILCAN - SOLO 2X hold in the server rankings?
For player hours in the last seven days, ANILCAN - SOLO 2X ranks #15,920, within the top 70% of ranked servers.
How to join
What's the process to join ANILCAN - SOLO 2X?
To join, open Rust, hit F1, and enter client.connect 78.189.33.35:28015. Or click Launch Rust on this page to open the game through Steam and connect.