Offline 212.22.85.104:35004 checked 31d ago
МОСКОВСКАЯ КЛАССИКА
Connect
srv = rust.server("212.22.85.104:35104")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 30, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 26 Sep, 13:09 UTC31d ago | 30 | NaN | running | 30 |
| 1 | Sat 26 Sep, 06:36 UTC31d ago | 50 | NaN | 0.3 days | 50 |
| 2 | Fri 25 Sep, 22:55 UTC32d ago | 50 | NaN | 0.3 days | 0 |
| 3 | Fri 25 Sep, 15:32 UTC32d ago | 50 | NaN | 0.3 days | 40 |
| 4 | Fri 25 Sep, 08:24 UTC32d ago | 50 | NaN | 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.
display(srv.map, srv.info())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 534 on average | 262/300 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 322 on average | 22/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 321 on average | 16/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 169/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 277 on average | 81/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 264 on average | 20/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does МОСКОВСКАЯ КЛАССИКА rank?
Over the last seven days МОСКОВСКАЯ КЛАССИКА sits at #5,870 on player hours, in the top 25% of ranked servers.
What population does МОСКОВСКАЯ КЛАССИКА carry?
МОСКОВСКАЯ КЛАССИКА returns no live count at this refresh, having last been seen 31 days 14 hours ago.
Server facts
What is the Rust version on МОСКОВСКАЯ КЛАССИКА?
Rust network protocol 2633 and build 165217 on Linux is what МОСКОВСКАЯ КЛАССИКА runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is МОСКОВСКАЯ КЛАССИКА, and is it up?
The latest sample has МОСКОВСКАЯ КЛАССИКА offline, with a last sighting 31 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 25 September 2026.
Which location does МОСКОВСКАЯ КЛАССИКА run from?
The name of МОСКОВСКАЯ КЛАССИКА points to Europe, even though no region tag is published; the region code is eu2. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 212.22.85.104:35004 is its address.
Rules, settings, map
Which settings and rules does МОСКОВСКАЯ КЛАССИКА run?
You will not find a gather rate in the string МОСКОВСКАЯ КЛАССИКА. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has МОСКОВСКАЯ КЛАССИКА selected?
Size 4,500, seed 1283756968: the procedural map on МОСКОВСКАЯ КЛАССИКА, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: ВАЙП БЫЛ 1Ч НАЗАД.
Wipe data
When does МОСКОВСКАЯ КЛАССИКА wipe, and on what schedule?
Irregular wipe times on МОСКОВСКАЯ КЛАССИКА leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 31 days 15 hours ago.
What is wipe day on МОСКОВСКАЯ КЛАССИКА like?
Across recent wipes the busiest point averaged 43 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does МОСКОВСКАЯ КЛАССИКА appear among Rust Data lists and 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 МОСКОВСКАЯ КЛАССИКА?
The game's server browser reads these tags from МОСКОВСКАЯ КЛАССИКА: gmrust (Game mode): Rust survival in its standard form; mp200 (Max players): Slot count: 200; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $reu2 (Region code): eu2 is the region code recorded; ^o (Oxide): Plugin framework: Oxide (uMod). The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to МОСКОВСКАЯ КЛАССИКА?
Enter client.connect 212.22.85.104:35004 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
