Online EU 37.230.137.223:27032 checked 6m ago
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST
Connect
srv = rust.server("37.230.137.223:27031")
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 17 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 bestTop 9% of all ranked servers, top 28% in EU. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Friday 30 October, 11:10 UTC, in 11h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 11h | Fri 30 Oct, 11:10 UTC | wipe |
| 1 | 6d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 14d 11h | Fri 13 Nov, 11:10 UTC | wipe |
| 3 | 28d 11h | Fri 27 Nov, 11:10 UTC | wipe |
| 4 | 34d 19h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 42d 11h | Fri 11 Dec, 11:10 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 29 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 11:10 UTC13d ago | 6 | NaN | running | 0 |
| 1 | Sat 3 Oct, 14:36 UTC26d ago | 4 | held half | 12.9 days | 2 |
| 2 | Sat 3 Oct, 06:44 UTC26d ago | 3 | NaN | 0.3 days | 0 |
| 3 | Thu 1 Oct, 19:58 UTC FW28d ago | 3 | NaN | 1.4 days | 0 |
| 4 | Fri 18 Sep, 12:23 UTC41d ago | 2 | held half | 13.3 days | 0 |
# 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 1337
- map
- Custom Map
- size
- 4500
- seed
- 1337
Server
srv.info()- address
- 37.230.137.223:27032
- region
- EU
- max players
- 300
- group limit
- 100 max
- wipe schedule
- biweekly
- last wipe
- 16 Oct 2026, 11:10 UTC
- hostname
- –
- first seen
- 13 Sep 2026
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 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 248 on average | 498/625 |
| 1 | Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 135 on average | 357/750 |
| 2 | Rusty Moose |EU Biweekly| | EU · groups of 12+ · biweekly · 56 on average | 434/575 |
| 3 | Rustoria.co - EU Medium | EU · groups of 12+ · biweekly · 39 on average | 304/375 |
| 4 | Rustopia.gg - EU Medium | EU · groups of 12+ · biweekly · 35 on average | 287/400 |
| 5 | Rustafied.com - EU Medium - Small | EU · groups of 16+ · biweekly · 22 on average | 174/300 |
Quick answers
From the figures on this page.
Player counts
What position does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST take in the server rankings?
On seven-day player hours МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is #2,115 overall and #815 in Europe, inside the top 9% of all ranked servers.
How full does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run?
The sample now reads 0 players for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, out of 300 slots. Over the last seven days it averaged 2 players and peaked at 9. The 48-hour sample puts the busiest hour at 21:00 UTC, averaging 2 players.
Server facts
How well does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST perform?
Server fps over the last 48 hours averages 112; the floor is 80. Entity numbers reached 125,335, and that includes buildings, deployables and the rest. The memory field tops out at 4,027 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
Version Rust network protocol 2635 and build 168909 on Linux is reported by МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. Steam updates your game for you, but the protocol must match to join.
How reliable is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and is it up?
Online is the state at the latest refresh for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. Count back 18 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST hosted?
In Europe, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST lists itself, using the EU tag. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 37.230.137.223:27032.
Rules, settings, map
Which rules apply on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and what settings?
No gather rate appears in the name: МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. Group size tops out at 100 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. Oxide plugins run on it. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.
Which map has МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST loaded?
Size 4,500, seed 1337: the procedural map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.
Wipe data
When does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST wipe, and on what schedule?
The tag sets the prediction: МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST has too few wipes on record to confirm its schedule. On Friday 30 October at 11:10 UTC the next wipe is due. The world it runs now was generated 13 days 12 hours ago. Its tags carry a wipe schedule of every two weeks.
On МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, what happens on wipe day?
Recent wipes averaged 4 players at their peak. 29 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags, lists
Which lists on Rust Data hold МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and which filters?
The Rust Data lists that МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST fits are: EU Rust servers, Rust community servers, unfiltered and Vanilla Rust servers. It appears under these filters on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
How should you read the server tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
These tags are published by МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp300 (Max players): Slot count: 300; ts100 (Group limit): No team may exceed 100; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^o (Oxide): The plugin framework in use is Oxide (uMod); EU (Europe): The server browser files it under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
Enter client.connect 37.230.137.223:27032 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.