At press time 11,830 servers89,192 players415 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 2,124

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST

Online EU 37.230.137.223:27032 checked 10m ago

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is a Rust server in Europe. At the last count it had 2 players of a possible 300; over the past week it averaged 2, with a peak of 9. It stands at No. 2,124 of the ranked servers, the top 10%, and No. 817 in Europe. It last wiped 13d ago, on a biweekly schedule, and the next wipe is expected on Friday 30 October. Its own tags class it as vanilla, oxide.

§ 1Attendance

AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

§ 2Performance

05010015020022:0007:0016:0002:0011:0020:00

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.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 10% of all ranked servers, top 28% in EU. Ranked on player hours over the last seven days.

§ 4The wipe schedulefrom its schedule tag

Next wipe Friday 30 October, 11:10 UTC, in 13h. Its biweekly schedule tag · low confidence

The rhythm
Usual gap7.2 days

between real wipes

On rhythm0%

of its recent wipes

Wipe-day peak4

players, last three wipes

Crowd held100%

of its cycles kept half the crowd

Coming wipes
Date, UTCHence
Fri 30 Oct, 11:1013h
Thu 5 Nov, 19:00 FW6d 21h
Fri 13 Nov, 11:1014d 13h
Fri 27 Nov, 11:1028d 13h
Thu 3 Dec, 19:00 FW34d 21h
Fri 11 Dec, 11:1042d 13h

The first 48 hours of its last wipes

Fri 16 OctSat 3 OctSat 3 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 29 hours in.

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers 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.

§ 6In its own wordsas the server describes itself

RE:RUST - Продвинутый сервер без доната для комфортной игры. Подходит как для новичков, так и опытных игроков. - Нет лимита на команды - Вайпы каждую вторую пятницу без сброса изучений - Активная администрация - Содержание шкафа снижено на 50% - Полностью без доната - EAC и RUST+ работают - Карты от 4000 квадратов

§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 Rustoria.co - EU East Medium690/725 EU · groups of 12+ · biweekly · 242 on average
  2. 2 Rustafied.com - EU Medium - Large523/750 EU · groups of 16+ · biweekly · 130 on average
  3. 3 Rusty Moose |EU Biweekly|628/650 EU · groups of 12+ · biweekly · 49 on average
  4. 4 Rustoria.co - EU Medium401/425 EU · groups of 12+ · biweekly · 34 on average
  5. 5 Rustopia.gg - EU Medium424/475 EU · groups of 12+ · biweekly · 30 on average
  6. 6 Rustafied.com - EU Medium - Small277/300 EU · groups of 16+ · biweekly · 19 on average

§ 8Questions answeredfrom the figures in this entry

Server record

On which Rust version does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST operate?

Rust network protocol 2635 and build 168909 on Linux is what МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs. The protocol must match on your game to join; the update comes through Steam.

Is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST up, and how steady is its uptime?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST currently answers as online. A restart came about 17 hours ago, by the server's own uptime figure. Of note: 167 of 168 hours up in the last 7 full days, or 99% of the time. The first sighting at Rust Server Stats was on 13 September 2026.

How does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST perform?

Server fps averaged 112 over the last 48 hours; the low was 80. Of note: 125,434 entities at the peak, counting buildings, deployables and the rest. The memory peak was 4,027 MB. What players feel as lag: fps running low and entities climbing.

Where does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST operate from?

Under the EU tag, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST lists itself in Europe. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. 37.230.137.223:27032 — that is the address.

Settings and map

What map does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST put players on?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs a procedural map, generated by the game, of size 4,500 with seed 1337. The map repeats with the same size and seed; this page links to it on RustMaps. The name of the map is: Custom Map.

What settings and rules does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run?

The name of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST states no rate for gathering. Group size does not exceed 100 players. Play is survival, gather, build and raid: the standard game. Player-versus-player fighting and raiding are enabled. The server browser shows it under Community, as a community server. Plugins run here: Oxide. Vanilla is its own description: unchanged rates, kits and rules: Facepunch's own game. VAC is enabled: Valve's anti-cheat.

Player record

What are the player numbers on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

2 players are on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST at present; the slot count is 300. Averaged across seven days, 2 players; the peak reached 9. Of the last 48 hours, 13:00 UTC drew the highest average: 2 players.

Where does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST sit in the rankings?

The player-hour table over seven days puts МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST at #2,124, and #817 for Europe, within the top 10% of all ranked servers.

Tag and list record

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST sits in which Rust Server Stats lists and filters?

These are the Rust Server Stats lists that include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: EU Rust servers: the records, Best Rust community servers and Best vanilla Rust servers. On the server list it comes up under these filters: 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.

Which meanings attach to the tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

gmrust (Game mode): Standard survival, as Rust plays it; mp300 (Max players): Slot count: 300; ts100 (Group limit): No team may exceed 100; v2635 (Protocol): Protocol 2635: joining needs the same game version; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): The region code is not set; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Unchanged rates, kits and rules: Facepunch's own game; ^o (Oxide): Plugin framework: Oxide (uMod); EU (Europe): Europe is where the server browser lists it — that is the set of tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes for the game's browser. The tags also carry its current players, its queue and the date its world was made. These appear at the top of this page.

Wipe schedule

Wipe day on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: what should be expected?

The average peak across recent wipes was 4 players. 29 hours after the latest wipe, the crowd peaked. The crowd held above half the peak until the next wipe in 100% of recent wipes.

On what schedule does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST wipe?

With the schedule unconfirmed by too few recorded wipes, the prediction on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST follows its tag. On Friday 30 October at 11:10 UTC the next wipe is due. The world now in play was generated 13 days 10 hours ago. A wipe every two weeks is published in its tags.

Connection

How does one connect to МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

To connect, open the console with F1 in Rust and enter client.connect 37.230.137.223:27032. The Launch Rust and join button on this page does the same through Steam.

§ 9Key to the tagswhat each one means

Published as mp300,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts100,^o

Game

gmrust
Game mode Standard survival, as Rust plays it.
mp300
Max players Slot count: 300.
ts100
Group limit No team may exceed 100.
v2635
Protocol Protocol 2635: joining needs the same game version.
cs168909
Build Build 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code The region code is not set.

Wipe schedule

^b
Biweekly Two weeks between wipes.

Difficulty

^v
Vanilla Unchanged rates, kits and rules: Facepunch's own game.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

Region

EU
Europe Europe is where the server browser lists it.

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.