StatusLive Servers online11,693 Players51,920 Populated3,092 Wiped · 3 h107 Interval5 min Date30 OCT 2026

DWG RG-S2120Server sheetchecked 11m ago

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

Online EU 37.230.137.223:27032 checked 11m ago

biweekly wipes vanillaoxide
Connect
Players now 0/ 300 0% full
7-day average2peak 9
Rank#2,120top 10% · #821 in EU
Last wipe13d agobiweekly schedule
Next wipe9hFri 30 Oct, 11:10 UTC
Fig. 1

Players

AveragePeak
0123403:0012:0022:0006:0015:0000:00

Hourly average and peak, UTC.

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

Server performance

05010015020003:0012:0022:0006:0015:0000: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

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

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

Coming wipes

  1. 9hFri 30 Oct, 11:10 UTC
  2. 6d 16hThu 5 Nov, 19:00 UTCFW
  3. 14d 9hFri 13 Nov, 11:10 UTC
  4. 28d 9hFri 27 Nov, 11:10 UTC
  5. 34d 16hThu 3 Dec, 19:00 UTCFW
  6. 42d 9hFri 11 Dec, 11:10 UTC

The first 48 hours of its last wipes

Fri 16 OctSat 3 OctSat 3 Oct
02468+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

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

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average
281 / 325
02
Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 138 on average
206 / 750
03
Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 61 on average
233 / 300
04
Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 42 on average
130 / 200
05
Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 39 on average
147 / 225
06
Rustafied.com - EU Medium - SmallEU · groups of 16+ · biweekly · 24 on average
67 / 300
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and is it online now?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is up at this moment. Counted from its reported uptime, the last restart was about 21 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

Is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST stable in the figures recorded?

The last 48 hours give an average of 112 server fps and a floor of 80. Counted at its highest: 124,959 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 4,027 MB. A climbing entity count and low fps are the source of what players feel as lag.

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

In Europe МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST lists itself, tagged EU. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 37.230.137.223:27032 is its address.

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

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

Counts

What does the population history show for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

At the last refresh, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST recorded 0 players across 300 slots. Averaged across seven days, the player count is 2, with a peak of 9. Over the last 48 hours the busiest hour was 21:00 UTC, at an average of 2 players.

Against other Rust servers, where is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST placed?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST also measures #821 in Europe on the same seven-day player-hour count, at #2,120 globally and in the top 10% of ranked servers.

Schedules

What happens on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST on the day of a wipe?

The recent wipes averaged a busiest count of 4 players. At 29 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.

What wipe schedule has been recorded for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Its tag is followed for the prediction: too few of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's wipes are on record to confirm the schedule. Friday 30 October at 11:10 UTC is the date its next wipe is due. The world it runs now was made 13 days 14 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Settings

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

Gather rate for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: not stated in the name. 100 players per group at most. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Community is its tab in the server browser. Oxide plugins are run on it. Vanilla is the label it uses: facepunch's game, unaltered: rates, kits and rules are as shipped. VAC is on: that is Valve's anti-cheat.

Which map has МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST loaded?

Seed 1337 and size 4,500 define the procedural map МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing. The map is named as follows: Custom Map.

Lists and filters

On Rust Graphs, which lists and filters contain МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

The Rust Graphs lists that carry МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST are: Europe servers, plotted, Rust community servers, plotted and Vanilla Rust servers. These filters on the server list return it: 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.

On МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, what is meant by each tag?

gmrust (Game mode): Survival in standard Rust style; mp300 (Max players): The slot count is 300; ts100 (Group limit): Team size is capped at 100; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): Facepunch's game, unaltered: rates, kits and rules are as shipped; ^o (Oxide): Plugin framework: Oxide (uMod); EU (Europe): In the server browser it appears under Europe are the tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

By what method do you join МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Enter client.connect 37.230.137.223:27032 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp300
Max players The slot count is 300.
ts100
Group limit Team size is capped at 100.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla Facepunch's game, unaltered: rates, kits and rules are as shipped.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

Region

EU
Europe 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.

KeyTag string decoded