МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST
Online EU 37.230.137.223:27032 checked 12m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 9% of all ranked servers, top 28% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 30 October, 11:10 UTC, in 10h. Its biweekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 10h | Fri 30 Oct, 11:10 UTC | its own |
| 6d 18h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 14d 10h | Fri 13 Nov, 11:10 UTC | its own |
| 28d 10h | Fri 27 Nov, 11:10 UTC | its own |
| 34d 18h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 42d 10h | Fri 11 Dec, 11:10 UTC | its own |
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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 11:10 UTC13d ago | 6 | – | running | 0 |
| Sat 3 Oct, 14:36 UTC26d ago | 4 | held half | 12.9 days | 2 |
| Sat 3 Oct, 06:44 UTC26d ago | 3 | – | 0.3 days | 0 |
| Thu 1 Oct, 19:58 UTC FW28d ago | 3 | – | 1.4 days | 0 |
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 371 / 425 |
| Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 137 on average | 276 / 750 |
| Rusty Moose |EU Biweekly| | EU · groups of 12+ · biweekly · 59 on average | 332 / 375 |
| Rustoria.co - EU Medium | EU · groups of 12+ · biweekly · 41 on average | 213 / 250 |
| Rustopia.gg - EU Medium | EU · groups of 12+ · biweekly · 37 on average | 229 / 275 |
| Rustafied.com - EU Medium - Small | EU · groups of 16+ · biweekly · 23 on average | 101 / 300 |
Quick answers
from the figures on this pageWipe data
The wipe schedule for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: what is it?
The prediction follows its tag, because too few of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's wipes are on record to confirm the schedule. Friday 30 October at 11:10 UTC is when its next wipe is due. The world now in play was created 13 days 13 hours ago. The tags carry an every-two-weeks wipe schedule.
On МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, what happens on wipe day?
The average busiest count over recent wipes is 4 players. The highest player count on the latest wipe arrived 29 hours in. Above half that peak until the next wipe held in 100% of recent wipes.
Server
Which location hosts МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
The EU tag on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST lists it in Europe. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 37.230.137.223:27032.
What Rust build does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run?
The platform is Linux, with Rust network protocol 2635 and build 168909 running on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. The protocol has to match before you can join; Steam updates it automatically.
How reliable is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and is it online now?
As of the latest refresh, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is online. Its reported uptime indicates a restart roughly 20 hours ago. Of 168 hours in the last 7 full days, 143 were up: 85%. The first sighting of it by Rust Server Analytics was on 13 September 2026.
Does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST perform well?
Server fps averaged 112 over the last 48 hours, with a floor of 80. Buildings, deployables and all other world objects brought the entity total to 124,959. Peak memory was 4,027 MB. Players experience lag as low fps combined with a rising entity count.
Tags
What do МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's tags stand for?
gmrust (Game mode): Survival in the standard Rust format; mp300 (Max players): Capacity of 300 slots; ts100 (Group limit): Team size is capped at 100; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set; ^b (Biweekly): A two-week wipe cycle; ^v (Vanilla): Stock Facepunch settings, with no rate changes, kits or extra rules; ^o (Oxide): The Oxide (uMod) plugin framework is installed; EU (Europe): Its browser listing sits in Europe are the tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
On Rust Server Analytics, which lists and filters feature МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
The following Rust Server Analytics lists count МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST among their servers: EU Rust servers: live population data, Community Rust servers, live and Vanilla Rust servers. These filters bring it up 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.
Population
Against other Rust servers, how does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST compare?
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST holds #2,115 on seven-day player hours and #817 in Europe, inside the top 9% of the ranked field.
What is the population of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST holds 0 players of its 300 slots as of the latest update. Seven-day figures: an average of 2 players and a peak of 9. Averaged over 48 hours, activity is highest at 21:00 UTC with 2 players.
Settings
How is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST configured, and what rules apply?
No gather rate is given in the name of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. The cap on group membership is 100 players. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Community is its listing; it is a community server. Oxide plugins are run. Vanilla is its own description: stock Facepunch settings, with no rate changes, kits or extra rules. The server runs with VAC, Valve's anti-cheat, enabled.
The map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: which one is it?
The game generates a procedural map of size 4,500 with seed 1337 for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. Size and seed fix the map, so a RustMaps view is available from this page. The name of the map is Custom Map.
Connection
What is the way onto МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
In the Rust console (F1), enter client.connect 37.230.137.223:27032. Launch Rust on this page also works, opening Rust through Steam and connecting you.