Skip to main content

Independent statistics on public Rust serversNot affiliated with Facepunch Studios

Latest count: 60,014 players on 11,706 servers
Rust CensusThe census of every public Rust server, counted and refreshed.

Statistical profileOnline

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

EU 37.230.137.223:27032 checked 35m ago

biweekly wipes vanillaoxide
Release date
Next release
In five minutes (00:35 UTC)
Source
Live server queries
Server address
37.230.137.223:27032
First recorded
13 September 2026

Connect to this server

Launch Rust and join

1. Main points

Players now

0/ 300

0% full

7-day average

2

peak 9

Rank

#2,120

top 10% · #821 in EU

Last wipe

13d ago

biweekly schedule

Next wipe

10h

Fri 30 Oct, 11:10 UTC

Main points

  • There were 0 players on it, 0% of its 300 slots.
  • Over the last seven days it averaged 2 players, with a peak of 9.
  • It ranks #2,120 of all ranked servers, the top 10%, and #821 in EU, on player hours over the last seven days.
  • Its current map went up 13d ago; the next wipe is expected Friday 30 October, 11:10 UTC, its biweekly schedule tag.

2. Players

Figure 1: Players on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST

Players now and over time, UTC

AveragePeak
0123402:0011:0021:0005:0014:0023:00

Hourly average and peak, UTC.

Source: Live server queries, Rust Census

3. Server performance

Figure 2: Frame rate, entities and memory

From asking the server directly; low fps and a climbing entity count mean lag

05010015020002:0011:0021:0005:0014:0023:00

Note

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.

4. Rank

Figure 3: Rank among all servers, daily

1 is best

RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Source: Live server queries, Rust Census

5. Wipe schedule

Patternfrom its schedule tag

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

Usual gap

7.2 days

between real wipes

On rhythm

0%

of its recent wipes

Wipe-day peak

4

players, last three wipes

Crowd held

100%

of its cycles kept half the crowd

Table 1: Coming wipes

Expected from its own rhythm and the force wipe

InDate and timeKind
10hFri 30 Oct, 11:10 UTCOwn schedule
6d 17hThu 5 Nov, 19:00 UTCForce wipe FW
14d 10hFri 13 Nov, 11:10 UTCOwn schedule
28d 10hFri 27 Nov, 11:10 UTCOwn schedule
34d 17hThu 3 Dec, 19:00 UTCForce wipe FW
42d 10hFri 11 Dec, 11:10 UTCOwn schedule

Figure 4: The first 48 hours of its last wipes

Players each hour, from the hour of the wipe

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.

Source: Live server queries, Rust Census

6. Wipes

Table 2: Wipes, newest first

Every wipe seen on this server

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

Notes

  1. 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.
  2. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Source: Live server queries, Rust Census

7. Map

Figure 5: Map of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST

4500 · seed 1337

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

Table 3: The world

As the server publishes it

MapCustom Map
Size4500
Seed1337

8. Server characteristics

Table 4: Characteristics of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST

What the server publishes and what was recorded

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

9. About this server

In its own words: the description the server publishes, unedited.

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

10. Similar servers

Table 5: Servers like this one

The same kind of game, then region, group limit, rate and wipes

ServerCharacteristicsPlayers
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average362 / 425
Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 138 on average273 / 750
Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 61 on average328 / 375
Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 42 on average210 / 250
Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 39 on average228 / 275
Rustafied.com - EU Medium - SmallEU · groups of 16+ · biweekly · 24 on average98 / 300

11. Quick answers

From the figures on this page.

Wipe schedule

This release records the wipe timetable for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: what is it?

Too few wipes of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST are recorded to confirm its schedule, so its tag is followed by the prediction. Friday 30 October at 11:10 UTC is the date of its next wipe. 13 days 13 hours have passed since this world was made. The tags list a fortnightly wipe schedule.

What should you expect on wipe day at МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

The average busiest point of its recent wipes drew 4 players. The peak of the latest wipe's crowd came 29 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe in 100% of cases.

Server details

Is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST up, and how well has it held up?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is online at the time of this release. The uptime it reports puts the last restart at about 20 hours ago. A total of 167 of 168 hours were up over 7 full days, which is 99% of the time. The first sighting of it by Rust Census was on 13 September 2026.

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

Over the last 48 hours, server fps averaged 112; the lowest reading was 80. Buildings, deployables and everything else in the world took the entity count to 124,959. Memory use reached 4,027 MB at its peak. What players experience as lag is low fps combined with a climbing entity count.

Which location does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run from?

In Europe МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST lists itself, with its EU tag. Rust Census does not look up where the machine stands; it shows where a server says it is. At 37.230.137.223:27032 it is addressed.

What version of Rust has been recorded on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Rust network protocol 2635 and build 168909 on Linux is the version МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs. To join, your game has to be on the same protocol; Steam handles the update.

Player figures

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

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST stands at 0 players from 300 slots in this release. Averaged over seven days: 2 players, with a peak of 9. The busiest hour in the last 48 hours was 21:00 UTC, with an average of 2 players.

How does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST compare with other servers in the rankings?

For seven-day player hours МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is ranked #2,120 and #821 in Europe, placing it in the top 10% of all ranked servers.

Tags, lists

Which Rust Census filters and lists cover МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

These Rust Census lists include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: EU Rust servers: the regional count, Community servers and Vanilla Rust servers. Under these filters it comes 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.

The tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: what do they indicate?

These are the tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp300 (Max players): 300 slots are available; ts100 (Group limit): No team may hold more than 100; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): This server carries no region code; ^b (Biweekly): A wipe is run once a fortnight; ^v (Vanilla): This is the unmodified game: rates, kits and rules as Facepunch ships them; ^o (Oxide): The plugin framework in use is Oxide (uMod); EU (Europe): In the server browser it appears under Europe. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.

Rules, map

What map is listed for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

The procedural map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is generated by the game, measures 4,500 and carries seed 1337. Because one size and seed give one map, RustMaps can display it from this page. The map carries the name: Custom Map.

How is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST configured, and what rules does it keep?

No gather rate is given in the name of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. 100 players is the recorded group limit. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. It appears under Community in the server browser. The plugin count is Oxide. Its own label is vanilla: this is the unmodified game: rates, kits and rules as Facepunch ships them. The server runs VAC, Valve's anti-cheat.

How to join

What is the way to join МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Enter client.connect 37.230.137.223:27032 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.

12. Server tags

What each tag this server publishes means: a glossary.

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

Game

gmrustGame mode Survival play, in the standard Rust format.
mp300Max players 300 slots are available.
ts100Group limit No team may hold more than 100.
v2635Protocol Your game must run protocol 2635 to join.
cs168909Build The server runs game build 168909.
ptrakNetworking RakNet is used, the standard network layer of the game.
$r?Region code This server carries no region code.

Wipe schedule

^bBiweekly A wipe is run once a fortnight.

Difficulty

^vVanilla This is the unmodified game: rates, kits and rules as Facepunch ships them.

Mods and access

^oOxide The plugin framework in use is Oxide (uMod).

Region

EUEurope In the server browser it appears 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.