RUST METRICSFlight deck · live data
Data live Servers11,808 Players73,203 Populated3,760 Fresh wipes 3 h145 Scan5 min
‹ All servers212.22.85.104:35004
Offline Full Queue Fresh wipe Wipe due No query

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

Offline 212.22.85.104:35004 checked 31d ago

oxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 30 /200

Players now

15% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#5,870top 25%
Last wipe31d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

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 gap0.3 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak43players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 26 Sep, 13:09 UTC31d ago 30 – running 30
Sat 26 Sep, 06:36 UTC31d ago 50 – 0.3 days 50
Fri 25 Sep, 22:55 UTC31d ago 50 – 0.3 days 0
Fri 25 Sep, 15:32 UTC32d ago 50 – 0.3 days 40
Fri 25 Sep, 08:24 UTC32d ago 50 – 0.3 days 20

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on МОСКОВСКАЯ КЛАССИКА?

At their busiest, its recent wipes drew 43 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does МОСКОВСКАЯ КЛАССИКА wipe, and when?

No next wipe can be predicted for МОСКОВСКАЯ КЛАССИКА, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 31 days 7 hours ago.

Lists and filters

Which tags does МОСКОВСКАЯ КЛАССИКА carry, and what do they mean?

Tags published by МОСКОВСКАЯ КЛАССИКА, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): Slots: 200; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $reu2 (Region code): Region code reading: eu2; ^o (Oxide): It runs Oxide, also known as uMod. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does МОСКОВСКАЯ КЛАССИКА appear in Rust Metrics lists and filters?

These Rust Metrics lists carry МОСКОВСКАЯ КЛАССИКА: EU Rust servers, checked and Rust community servers: live readings. Check: filters. On the server list it appears under these: 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.

Player count

What position does МОСКОВСКАЯ КЛАССИКА hold among Rust servers?

Ranking for МОСКОВСКАЯ КЛАССИКА: #5,870 on seven-day player hours, top 25% of all ranked servers.

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

МОСКОВСКАЯ КЛАССИКА is not responding; status offline, last seen 31 days 5 hours ago.

Operator and location

Which location does МОСКОВСКАЯ КЛАССИКА run from?

Reading: location. None in the tags, but the name of МОСКОВСКАЯ КЛАССИКА points to Europe, with region code eu2. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 212.22.85.104:35004.

What Rust version is МОСКОВСКАЯ КЛАССИКА on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by МОСКОВСКАЯ КЛАССИКА. Check: protocol. To join, your game must match; Steam handles the update.

Is МОСКОВСКАЯ КЛАССИКА up, and how often does it stay up?

Reading: offline. МОСКОВСКАЯ КЛАССИКА last answered 31 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Rules and settings

What rules does МОСКОВСКАЯ КЛАССИКА enforce, and what are its settings?

Check: gather rate. The name МОСКОВСКАЯ КЛАССИКА does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.

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

From seed 1283756968, the game generates the procedural map on МОСКОВСКАЯ КЛАССИКА. Its size is 4,500. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name ВАЙП БЫЛ 1Ч НАЗАД.

Connection

What do you do to join МОСКОВСКАЯ КЛАССИКА?

To join: start Rust, press F1 and type client.connect 212.22.85.104:35004. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players Slots: 200.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$reu2
Region code Region code reading: eu2.

Mods and access

^o
Oxide It runs Oxide, also known as 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.