Rust Server TrendsSeismic network · station log
Recording Stations11,684 Players38,205 Active2,919 Wipes · 3 h95 48 h

Station GE-15920 · no signal

ANILCAN - SOLO 2X

Offline 78.189.33.35:28015 checked 26d ago

2x
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,920
top 70%
Last wipe
26d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station GE-15920 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Atlas - EU 2X Monthly Solo/Duo/Trio/Quad | Vanilla+ | No BP Wip EU · no group limit · 2x · 70 on average
66/ 100
Atlas - 2X Monthly | JUST WIPED 29.10 no group limit · 2x · 65 on average
65/ 100
MIRAGE RUST | Weekly 2x | 29.10 no group limit · 2x · 64 on average
44/ 100
RustSide Solo/Duo/Trio 2x | JUST FULLWIPED 29.10 no group limit · 2x · 60 on average
68/ 100
[EU] Stevious 2x Main | Vanilla | 29.10 EU · no group limit · 2x · 55 on average
51/ 100
Survivors.gg [ 2x Vanilla ] | JUST WIPED 29.10 no group limit · 2x · 50 on average
31/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on ANILCAN - SOLO 2X?

The map on ANILCAN - SOLO 2X is procedural, produced by the game.

Which settings and rules apply on ANILCAN - SOLO 2X?

Going by its name, ANILCAN - SOLO 2X runs 2x gather. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on ANILCAN - SOLO 2X right now?

ANILCAN - SOLO 2X is not responding at this moment and is offline, last seen 26 days 11 hours ago.

How does ANILCAN - SOLO 2X rank against other Rust servers?

On player hours for the past week, ANILCAN - SOLO 2X sits at #15,920, which puts it inside the top 70% of every ranked server.

Operator and location

How reliably does ANILCAN - SOLO 2X stay online?

As recorded now, ANILCAN - SOLO 2X is not reachable, the last contact having been 26 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 2 October 2026.

Which region does ANILCAN - SOLO 2X run from?

No region comes from ANILCAN - SOLO 2X, though its region code is ger. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 78.189.33.35:28015 is the address it uses.

What build of Rust does ANILCAN - SOLO 2X use?

ANILCAN - SOLO 2X is running Rust network protocol 2617 and build 140534 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

How often does ANILCAN - SOLO 2X wipe, and on which days?

Too few wipes of ANILCAN - SOLO 2X are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 26 days 12 hours is how long the current world has been running.

Server tags

What do the server tags on ANILCAN - SOLO 2X mean?

Tags published by ANILCAN - SOLO 2X and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2617 (Protocol): To connect, your game must be on the same protocol, 2617; cs140534 (Build): It runs game build 140534; ptrak (Networking): The network layer is RakNet, the game's standard; $rger (Region code): You'll see it listed with the region code ger. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does ANILCAN - SOLO 2X appear?

These Rust Server Trends lists include ANILCAN - SOLO 2X: 2x Rust servers, listed live and Rust community servers without the side modes. 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.

Connecting

How do you connect to ANILCAN - SOLO 2X?

You can connect by pressing F1 in Rust and typing client.connect 78.189.33.35:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$rger,v2617,gmrust,cs140534,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players Slots: 10.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2617
Protocol To connect, your game must be on the same protocol, 2617.
cs140534
Build It runs game build 140534.
ptrak
Networking The network layer is RakNet, the game's standard.
$rger
Region code You'll see it listed with 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.