Rust StatisticsWorking papers on every public Rust server · 41,758 players now

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

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 37.230.137.223:27032

Abstract

We describe the public Rust server МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, reached at 37.230.137.223:27032 and hosted in EU. At the last check it held 0 of 300 places, against a seven-day mean of 2 and a peak of 91. It ranks #2,131 of all servers, the top 10%, and #824 in EU. It last wiped 13d ago on a published biweekly schedule; the next wipe is expected Friday 30 October, 11:10 UTC, its biweekly schedule tag.

Keywordsbiweekly wipes vanilla oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/3000% full
In the queue0no queue
Seven-day mean2peak 9, 48 h peak 3
Rank2#2,131top 10%; #824 in EU
Last wipe13d agobiweekly schedule
Next wipe36hFri 30 Oct, 11:10 UTC

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0123405:0014:0000:0008:0017:0002:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020005:0014:0000:0008:0017:0002:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 10% of all ranked servers, the top 28% in EU. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: from its schedule tag

The next wipe is expected Friday 30 October, 11:10 UTC, in 6h. Its biweekly schedule tag (low confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap7.2 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak4players, last three wipes
Crowd held100%of its cycles kept half the crowd
Table 3: Coming wipes, as expected.
When (UTC)InKind
Fri 30 Oct, 11:106hits own schedule
Thu 5 Nov, 19:006d 14hforce wipefw
Fri 13 Nov, 11:1014d 6hits own schedule
Fri 27 Nov, 11:1028d 6hits own schedule
Thu 3 Dec, 19:0034d 14hforce wipefw
Fri 11 Dec, 11:1042d 6hits own schedule
Fri 16 OctSat 3 OctSat 3 Oct
02468+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 16 Oct, 11:1013d ago 6 – running 0
Sat 3 Oct, 14:3626d ago 4 held half 12.9 d 2
Sat 3 Oct, 06:4426d ago 3 – 0.3 d 0
Thu 1 Oct, 19:58fw28d ago 3 – 1.4 d 0
Fri 18 Sep, 12:2341d ago 2 held half 13.3 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST
Figure 5: The map: Custom Map, size 4500, seed 1337.
Table 5: The server's published settings.
Address37.230.137.223:27032
RegionEU
Max players300
Group limit100 max
Wipe schedulebiweekly
Last wipe16 Oct 2026, 11:10 UTC
Hostname–
First seen13 Sep 2026
MapCustom Map
Size4500
Seed1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are eu rust server list [2], rust community servers listed [3], vanilla rust servers [4] and predicted wipe schedule [5].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 258 on average281/300
Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 141 on average106/250
Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 66 on average162/200
Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 45 on average83/200
Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 42 on average109/200
Rustafied.com - EU Medium - SmallEU · groups of 16+ · biweekly · 25 on average47/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1How well does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run?

Its average server fps over the last 48 hours was 110, with a minimum of 80. Buildings, deployables and all other world objects counted together reached a maximum of 124,959 entities. Memory use peaked at 4,027 MB. When fps is low and entity count climbs, players feel lag.

A.2What is the location of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

In Europe, according to its own listing, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST appears with the EU tag. Rust Statistics does not look up the machine's location; it shows where the server says it is. 37.230.137.223:27032 is its address.

A.3What is the online status and reliability of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

At the present moment, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is online. The uptime it reports indicates a restart about 23 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. Its first appearance in Rust Statistics's records is 13 September 2026.

A.4What version of Rust is run on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is running Rust network protocol 2635 and build 168909 on the Linux operating system. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5What schedule does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST follow for wipes?

The prediction follows the tag, as МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's recorded wipes are too few to confirm its schedule. On Friday 30 October at 11:10 UTC the next wipe is expected. The current world has been running for 13 days 17 hours. A fortnightly wipe schedule appears in its tags.

A.6What happens on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST when wipe day arrives?

Recent wipes saw an average peak of 4 players. The crowd reached its maximum 29 hours after the latest wipe. Half the peak was sustained until the next wipe in 100% of recent wipes.

Population

A.7What is the rank of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST among Rust servers?

The seven-day player-hours ranking gives МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST #2,131, in the top 10% of ranked servers and #824 in Europe.

A.8What is the population level of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

On МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, 0 of the 300 slots are occupied at present. Over the last week the count averages 2 players and reaches 9 at its height. Averaging 2 players, 21:00 UTC was the busiest hour of the past 48.

Tags and filters

A.9How should the tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST be interpreted?

gmrust (Game mode): This is survival as standard Rust plays; mp300 (Max players): 300 slots are available; ts100 (Group limit): A team holds no more than 100; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^b (Biweekly): It wipes on a two-week cycle; ^v (Vanilla): This is the game as Facepunch ships it, with rates, kits and rules unaltered; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; EU (Europe): The server browser lists this server under Europe: these are the tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST be found among the Rust Statistics lists and filters?

The Rust Statistics lists that МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST fits are: European Rust servers, Rust community servers, measured and Vanilla Rust servers. It appears under the following 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.

Settings and map

A.11What are the settings and rules that govern МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Its name carries no gather rate for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. A group holds at most 100 players. survival is the game mode here; gathering, building and raiding, as the game is usually played. Players may raid and fight one another. Community is its category in the server browser. Plugins number Oxide on this server. By its own label, vanilla, this is the game as Facepunch ships it, with rates, kits and rules unaltered. The server has VAC on, Valve's anti-cheat.

A.12On which map does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST take place?

The game generates МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's procedural map at size 4,500, from seed 1337. Equal size and seed yield an identical map, which this page offers to view on RustMaps. The map is named Custom Map.

How to join

A.13How do you connect to МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Press F1 inside Rust to open the console and enter client.connect 37.230.137.223:27032. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp300,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts100,^o.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp300Max players. 300 slots are available.
ts100Group limit. A team holds no more than 100.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. The game build is 168909.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Wipe schedule
^bBiweekly. It wipes on a two-week cycle.
Difficulty
^vVanilla. This is the game as Facepunch ships it, with rates, kits and rules unaltered.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
Region
EUEurope. The server browser lists this server under Europe.

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.

Appendix CAbout this server, in its own words

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

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Eu rust server list. ruststatistics.org/top-eu-rust-servers.
  3. [3]Rust Statistics. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
  4. [4]Rust Statistics. Vanilla rust servers. ruststatistics.org/top-vanilla-rust-servers.
  5. [5]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.