Holds a respectable place: #5,870 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
9/ 100
F
Lost ground: down 4,816 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.
AveragePeakWipe
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
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Rank
daily · 1 is best
RankRank in region
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 30, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 UTC32d 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.
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. You can connect at 212.22.85.104:35004.
How dependable is МОСКОВСКАЯ КЛАССИКА, and is it online at the moment?
At this moment, МОСКОВСКАЯ КЛАССИКА is offline; the last time it was seen was 31 days 13 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 25 September 2026, Rust Server Score saw it for the first time.
What Rust version is МОСКОВСКАЯ КЛАССИКА on?
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.
Resets
When does МОСКОВСКАЯ КЛАССИКА wipe, and how often?
No next wipe can be predicted for МОСКОВСКАЯ КЛАССИКА, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 31 days 14 hours.
What should you expect from wipe day on МОСКОВСКАЯ КЛАССИКА?
Recent wipes have peaked at 43 players on average. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does МОСКОВСКАЯ КЛАССИКА sit among Rust servers?
Over the last seven days, МОСКОВСКАЯ КЛАССИКА has #5,870 for player hours, in the top 25% of all ranked servers.
What does the population on МОСКОВСКАЯ КЛАССИКА look like?
МОСКОВСКАЯ КЛАССИКА is offline at the moment; the last time it was seen was 31 days 13 hours ago.
Tags
How should you read the tags on МОСКОВСКАЯ КЛАССИКА?
gmrust (Game mode): Rust survival, played by the standard rules; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $reu2 (Region code): eu2 is the region code this server uses; ^o (Oxide): Plugin framework: Oxide (uMod) are the tags МОСКОВСКАЯ КЛАССИКА publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature МОСКОВСКАЯ КЛАССИКА?
These Rust Server Score lists count МОСКОВСКАЯ КЛАССИКА among them: European Rust servers, graded and Best community servers, graded. You can find it under these server-list filters: 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
Which rules does МОСКОВСКАЯ КЛАССИКА enforce, and what are its settings?
The name of МОСКОВСКАЯ КЛАССИКА gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on МОСКОВСКАЯ КЛАССИКА?
The game generates the procedural map on МОСКОВСКАЯ КЛАССИКА at size 4,500 with seed 1283756968. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: ВАЙП БЫЛ 1Ч НАЗАД.
Getting in
How should you connect to МОСКОВСКАЯ КЛАССИКА?
Enter client.connect 212.22.85.104:35004 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
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 playersThe server holds 200 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$reu2
Region codeeu2 is the region code this server uses.
Mods and access
^o
OxidePlugin framework: 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).