Rust Data

rustdata.spaceservers185.135.82.84:35104.ipynb

Run all rust-data · live

‹ All servers

Offline 185.135.82.84:35004 checked 32d ago

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

oxide

Connect

srv = rust.server("185.135.82.84:35104")
print(srv.connect_command)

Right now

srv.summary()
players now 40/200 # 20% full
7-day average 0 # peak –
rank #5,445 # top 23%
last wipe 32d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap0.3 daysbetween real wipes
wipe-day peak40players, last three wipes

The first 48 hours of its last wipes

Sun 27 SepSun 27 Sep
010203040+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 27 Sep, 09:47 UTC32d ago 40 NaN running 40
1 Sun 27 Sep, 02:43 UTC32d ago 40 NaN 0.3 days 40

# 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.

display(srv.map, srv.info())

Map

4500 · seed 1283756968
Map of МОСКОВСКАЯ КЛАССИКА
map
ВАЙП БЫЛ 41М НАЗАД
size
4500
seed
1283756968

Server

srv.info()
address
185.135.82.84:35004
region
– · eu2
max players
200
group limit
8, the default
wipe schedule
–
last wipe
27 Sep 2026, 11:17 UTC
hostname
–
first seen
27 Sep 2026

About this server · in its own words

print(srv.description)
Мы обеспечиваем отличный геймплей и качественное управление сервером на выделенных машинах в московском дата-центре. • Размер группы: без ограничений • Ключевые особенности: - Настоящий ванильный опыт (без pay-to-win) - Карты, подобранные специально под сервер - Голосование сообщества за карту перед вайпом - Плавный геймплей без лагов и просадок - Активное и дружелюбное сообщество - Выделенное железо нового поколения для максимальной производительности - Регулярные обновления и поддержка администрации Наша команда следит за честной игрой и обеспечивает поддержку высшего уровня. За помощью — напишите нам в Telegram.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 513 on average527/550
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average411/450
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average65/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average70/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average54/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 238 on average170/200

Quick answers

From the figures on this page.

Player counts

How does МОСКОВСКАЯ КЛАССИКА compare in the rankings?

Over the last seven days МОСКОВСКАЯ КЛАССИКА sits at #5,445 on player hours, in the top 23% of ranked servers.

How many players does МОСКОВСКАЯ КЛАССИКА hold at once?

МОСКОВСКАЯ КЛАССИКА returns no live count at this refresh, having last been seen 32 days 1 hours ago.

Server facts

What Rust version does МОСКОВСКАЯ КЛАССИКА run?

Rust network protocol 2633 and build 165217 on Linux is what МОСКОВСКАЯ КЛАССИКА runs. Joining needs the same protocol on your game; Steam handles the update.

Is МОСКОВСКАЯ КЛАССИКА up, and what does its uptime show?

МОСКОВСКАЯ КЛАССИКА is offline at this refresh; the last response came 32 days 1 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 27 September 2026.

In which location is МОСКОВСКАЯ КЛАССИКА hosted?

No region tag is published by МОСКОВСКАЯ КЛАССИКА, though its name points to Europe; the region code is eu2. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 185.135.82.84:35004.

Settings and map

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

No gather rate appears in the name: МОСКОВСКАЯ КЛАССИКА. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

Which map has МОСКОВСКАЯ КЛАССИКА loaded?

The game generates the map on МОСКОВСКАЯ КЛАССИКА: procedural, size 4,500, seed 1283756968. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: ВАЙП БЫЛ 41М НАЗАД.

Wipe schedule

When does МОСКОВСКАЯ КЛАССИКА wipe, and how often?

A rhythm cannot be read from the wipes of МОСКОВСКАЯ КЛАССИКА on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 32 days 2 hours ago.

On МОСКОВСКАЯ КЛАССИКА, what happens on wipe day?

The average peak over recent wipes is 40 players. 0 hours after the latest wipe, the crowd reached its peak.

Lists and tags

Which lists on Rust Data hold МОСКОВСКАЯ КЛАССИКА, and which filters?

On Rust Data, МОСКОВСКАЯ КЛАССИКА appears in these lists: EU Rust servers and Rust community servers, unfiltered. These filters bring it up on the server list: 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 should you read the server tags on МОСКОВСКАЯ КЛАССИКА?

Read by the game's server browser, the tags МОСКОВСКАЯ КЛАССИКА publishes are: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $reu2 (Region code): The row gives eu2 as its region code; ^o (Oxide): The plugin framework in use is Oxide (uMod). Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way into МОСКОВСКАЯ КЛАССИКА?

The manual route: launch Rust, F1, then client.connect 185.135.82.84:35004. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp200
Max players Slot count: 200.
ts8
Group limit Team limit of 8, as shipped by default.
v2633
Protocol To join, your game must run protocol 2633.
cs165217
Build Recorded game build: 165217.
ptrak
Networking The network layer is RakNet, standard for the game.
$reu2
Region code The row gives eu2 as its region code.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).

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.

Rust Data 72,372 players 11,823 servers online