Rust Server TrendsSeismic network · station log
Recording Stations11,611 Players34,878 Active2,847 Wipes · 3 h62 48 h

Station EU-5870 · no signal

МОСКОВСКАЯ КЛАССИКА

Offline 212.22.85.104:35004 checked 31d ago

oxide
Connect
Players now
30/ 200
15% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#5,870
top 25%
Last wipe
31d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station EU-5870 · 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
30of 200 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, measured since 25 Sep. 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
12k4k6k8k25 Sep27 Sep28 Sep30 Sep1 Oct3 Oct

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

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
0.3 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
43players, last three wipes

The first 48 hours of its last wipes

Sat 26 SepSat 26 SepFri 25 Sep
020406080+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 30, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 26 Sep, 13:09 UTC31d ago M0.0steady 30 – running 30
Sat 26 Sep, 06:36 UTC31d ago M0.0steady 50 – 0.3 days 50
Fri 25 Sep, 22:55 UTC32d ago M1.7rising 50 – 0.3 days 0
Fri 25 Sep, 15:32 UTC32d ago M1.0rising 50 – 0.3 days 40
Fri 25 Sep, 08:24 UTC32d ago M1.5rising 50 – 0.3 days 20

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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 532 on average
214/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 327 on average
15/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 325 on average
19/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
115/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 278 on average
40/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 264 on average
42/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on МОСКОВСКАЯ КЛАССИКА?

Generated by the game, the map on МОСКОВСКАЯ КЛАССИКА is procedural, size 4,500 with seed 1283756968. From this page you can look at it on RustMaps, since the same size and seed give the same map. The name of its map is ВАЙП БЫЛ 1Ч НАЗАД.

Which settings and rules apply on МОСКОВСКАЯ КЛАССИКА?

You will find no gather rate in the name of МОСКОВСКАЯ КЛАССИКА. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on МОСКОВСКАЯ КЛАССИКА?

МОСКОВСКАЯ КЛАССИКА is not responding at this moment and is offline, last seen 31 days 12 hours ago.

How does МОСКОВСКАЯ КЛАССИКА rank against other Rust servers?

On player hours for the past week, МОСКОВСКАЯ КЛАССИКА sits at #5,870, which puts it inside the top 25% of every ranked server.

Server details

How reliably does МОСКОВСКАЯ КЛАССИКА stay online?

As recorded now, МОСКОВСКАЯ КЛАССИКА is not reachable, the last contact having been 31 days 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 25 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is МОСКОВСКАЯ КЛАССИКА hosted?

Its region code is eu2 and its name points to Europe, but МОСКОВСКАЯ КЛАССИКА publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 212.22.85.104:35004.

Which Rust version is МОСКОВСКАЯ КЛАССИКА running?

Rust network protocol 2633 and build 165217 on Linux is what МОСКОВСКАЯ КЛАССИКА runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

What does wipe day look like on МОСКОВСКАЯ КЛАССИКА?

The recent wipes averaged a busiest count of 43 players. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does МОСКОВСКАЯ КЛАССИКА run its wipes?

There is no next wipe to predict at МОСКОВСКАЯ КЛАССИКА, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 31 days 13 hours is how long the current world has been running.

Lists and tags

What do the server tags on МОСКОВСКАЯ КЛАССИКА mean?

The game's server browser reads the tags МОСКОВСКАЯ КЛАССИКА publishes: gmrust (Game mode): Survival in standard Rust; mp200 (Max players): The server has 200 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): It runs game build 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $reu2 (Region code): Region code: eu2; ^o (Oxide): A plugin framework, Oxide (uMod), runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does МОСКОВСКАЯ КЛАССИКА appear?

These Rust Server Trends lists include МОСКОВСКАЯ КЛАССИКА: EU Rust servers and Rust community servers without the side modes. On the server list, the filters it matches are: Region: Europe; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Players now: At least 10.

How to join

What steps get you onto МОСКОВСКАЯ КЛАССИКА?

To join, enter client.connect 212.22.85.104:35004 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp200,ptrak,$reu2,v2633,gmrust,cs165217,ts8,^o

Game

gmrust
Game mode Survival in standard Rust.
mp200
Max players The server has 200 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build It runs game build 165217.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$reu2
Region code Region code: eu2.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.

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.