Rust Server TrendsSeismic network · station log
Recording Stations11,742 Players66,506 Active3,391 Wipes · 3 h202 48 h

Station EU-2115 · recording

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

Online EU 37.230.137.223:27032 checked 8m ago

biweekly wipes vanillaoxide
Connect
Players now
0/ 300
0% full
Motion · 24 h
M0.3rising
+2 players on the day
7-day average
2
peak 9
Rank
#2,115
top 9% · #815 in EU
Last wipe
13d ago
biweekly schedule
Next wipe
11h
Fri 30 Oct, 11:10 UTC
Seismic record · station EU-2115 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 300 slots
Motion · 24 h
M0.3rising+2 players
Sharpest hour
−2into Wed 15:00 UTC
Peak · 48 h
3most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123400:0009:0019:0004:0013:0022:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020000:0009:0019:0004:0013:0022: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Expected events

Wipe schedule

from its schedule tag

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

usual gap
7.2 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
4players, last three wipes
crowd held
100%of its cycles kept half the crowd

Coming wipes

  1. 11hFri 30 Oct, 11:10 UTC
  2. 6d 19hThu 5 Nov, 19:00 UTCFW
  3. 14d 11hFri 13 Nov, 11:10 UTC
  4. 28d 11hFri 27 Nov, 11:10 UTC
  5. 34d 19hThu 3 Dec, 19:00 UTCFW
  6. 42d 11hFri 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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 16 Oct, 11:10 UTC13d ago M0.8rising 6 – running 0
Sat 3 Oct, 14:36 UTC26d ago M0.3rising 4 held half 12.9 days 2
Sat 3 Oct, 06:44 UTC26d ago M0.5rising 3 – 0.3 days 0
Thu 1 Oct, 19:58 UTC FW28d ago M0.5rising 3 – 1.4 days 0
Fri 18 Sep, 12:23 UTC41d ago M0.3rising 2 held half 13.3 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 248 on average
461/ 525
Rustafied.com - EU Medium - Large EU · groups of 16+ · biweekly · 135 on average
323/ 750
Rusty Moose |EU Biweekly| EU · groups of 12+ · biweekly · 56 on average
386/ 450
Rustoria.co - EU Medium EU · groups of 12+ · biweekly · 39 on average
274/ 325
Rustopia.gg - EU Medium EU · groups of 12+ · biweekly · 35 on average
262/ 325
Rustafied.com - EU Medium - Small EU · groups of 16+ · biweekly · 22 on average
149/ 300
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

The procedural map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is size 4,500 with seed 1337, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. The name of its map is Custom Map.

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

No gather rate appears in the name of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. The group limit is 100 players. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Community, as a community server. Oxide is the plugin framework it runs. It describes itself as vanilla, which means rates, kits and rules are as Facepunch ships them. The server has VAC on, Valve's anti-cheat.

Population

How many players are recorded on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST right now?

A reading taken now shows 0 players on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, which has 300 slots. Across seven days this server recorded an average of 2 players and a peak of 9. The busiest point in the last 48 hours came at 21:00 UTC, averaging 2 players.

How does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST rank against other Rust servers?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is #815 in Europe and #2,115 worldwide on the past week's player hours, within the top 9% of ranked servers.

Server details

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

Right now, you can reach МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. Going by the uptime figure it reports, it restarted about 19 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST hold a steady tick rate?

The 48-hour average is 112 server fps; 80 is the lowest observed. The world held up to 125,335 entities at its peak, buildings and deployables included. It reached a ceiling of 4,027 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.

Where in the world is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST hosted?

The EU tag is how МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST lists itself in Europe. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 37.230.137.223:27032.

What build of Rust does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST use?

МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

4 players, on average, was the busiest crowd at its recent wipes. 29 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

On what timetable does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run its wipes?

Its schedule cannot be confirmed, as too few of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's wipes are on record; the prediction follows its tag instead. The date of its next wipe is Friday 30 October at 11:10 UTC. 13 days 12 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.

Server tags

What do the server tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST mean?

Tags published by МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp300 (Max players): Slots: 300; ts100 (Group limit): The team limit is 100; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^o (Oxide): Oxide (uMod) is the plugin framework running here; EU (Europe): In the server browser it appears under Europe. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST appear?

These Rust Server Trends lists include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: EU Rust servers, Rust community servers without the side modes and Vanilla Rust servers, recorded live. 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.

How to join

What steps get you onto МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Enter client.connect 37.230.137.223:27032 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp300
Max players Slots: 300.
ts100
Group limit The team limit is 100.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla Rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.