Holds a respectable place: #5,445 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
17/ 100
F
Lost ground: down 3,644 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (B); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 23% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
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
Players each hour, from the hour of the wipe. The latest peaked at 40, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 27 Sep, 09:47 UTC32d ago
40
–
running
40
Sun 27 Sep, 02:43 UTC32d ago
40
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The name of МОСКОВСКАЯ КЛАССИКА points to Europe even though no region tag is published, and the region code is eu2. Rust Server Score takes the server's word for its location and does not trace the hardware. 185.135.82.84:35004 is the address to use.
How dependable is МОСКОВСКАЯ КЛАССИКА, and is it online at the moment?
At this moment, МОСКОВСКАЯ КЛАССИКА is offline; the last time it was seen was 32 days 2 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 27 September 2026.
Which Rust version is МОСКОВСКАЯ КЛАССИКА running?
The server МОСКОВСКАЯ КЛАССИКА is on Rust network protocol 2633 and build 165217 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does МОСКОВСКАЯ КЛАССИКА wipe its map?
МОСКОВСКАЯ КЛАССИКА has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 32 days 2 hours.
What happens on МОСКОВСКАЯ КЛАССИКА when wipe day arrives?
Across its recent wipes, the busiest moments averaged 40 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does МОСКОВСКАЯ КЛАССИКА place in the wider field of Rust servers?
Over the last seven days, МОСКОВСКАЯ КЛАССИКА has #5,445 for player hours, in the top 23% of all ranked servers.
How many players does МОСКОВСКАЯ КЛАССИКА usually have?
The last sighting of МОСКОВСКАЯ КЛАССИКА was 32 days 2 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on МОСКОВСКАЯ КЛАССИКА?
The game's browser takes its cue from the tags МОСКОВСКАЯ КЛАССИКА has set: gmrust (Game mode): Rust survival, played by the standard rules; mp200 (Max players): Its slot count is 200; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $reu2 (Region code): Region code: eu2; ^o (Oxide): The plugin framework in use is Oxide (uMod). The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show МОСКОВСКАЯ КЛАССИКА?
These Rust Server Score lists count МОСКОВСКАЯ КЛАССИКА among them: European Rust servers, graded and Best community servers, graded. 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.
Server rules
How is МОСКОВСКАЯ КЛАССИКА set up, and what rules does it keep?
You will find no gather rate in the name of МОСКОВСКАЯ КЛАССИКА. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
МОСКОВСКАЯ КЛАССИКА runs which map?
A procedural map of size 4,500 and seed 1283756968, generated by the game, is what МОСКОВСКАЯ КЛАССИКА runs. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: ВАЙП БЫЛ 41М НАЗАД.
Getting in
What is the way to join МОСКОВСКАЯ КЛАССИКА?
To connect, start Rust, press F1, and type client.connect 185.135.82.84:35004. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$reu2,v2633,gmrust,cs165217,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp200
Max playersIts slot count is 200.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$reu2
Region codeRegion code: eu2.
Mods and access
^o
OxideThe 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.
A term to build on. Strongest in standing (B); momentum is the one to work on (F).