RUST METRICSFlight deck · live data
Data live Servers11,706 Players60,014 Populated3,275 Fresh wipes 3 h133 Scan5 min
‹ All servers37.230.137.223:27032
Online Full Queue Fresh wipe Wipe due No query

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

Online EU 37.230.137.223:27032 checked 34m ago

biweekly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Thu 23:00 UTC
0 75 150 225 300 PAX 0 /300

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 114 SERVER FPS

Server fps

48 h low 80 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 122,068 ×1000

Entities

48 h range 107,374–124,959 · memory 3,592 MB
1239 ET SINCE RESTART 20:00

Uptime

20 h 0 min since its last restart, at the last reading
7-day average2peak 9
Rank#2,120top 10% · #821 in EU
Last wipe13d agobiweekly schedule
Next wipe10hFri 30 Oct, 11:10 UTC
Memory3,592MB48 h peak 3 players
REC 1

Players

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

Hourly average and peak, UTC.

REC 2

Server performance

05010015020002:0011:0021:0005:0014:0023: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.

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 11:10 UTC, in 10h. 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. WPT 1Fri 30 Oct, 11:10 UTC10h
  2. WPT 2Thu 5 Nov, 19:00 UTC6d 17hFW
  3. WPT 3Fri 13 Nov, 11:10 UTC14d 10h
  4. WPT 4Fri 27 Nov, 11:10 UTC28d 10h
  5. WPT 5Thu 3 Dec, 19:00 UTC34d 17hFW
  6. WPT 6Fri 11 Dec, 11:10 UTC42d 10h

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.

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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Reset cycle

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

An average of 4 players came at the busiest on its recent wipes. 29 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

How often does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST wipe, and when?

The prediction follows its tag, because too few of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's wipes are on record to confirm its schedule. Friday 30 October at 11:10 UTC is when its next wipe is due. 13 days 13 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tags

Which tags does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp300 (Max players): 300 slots in total; ts100 (Group limit): You may team up with at most 100; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^o (Oxide): Plugin framework in use: Oxide (uMod); EU (Europe): Its browser listing: Europe from МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

These Rust Metrics lists carry МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: EU Rust servers, checked, Rust community servers: live readings and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: 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.

Population

What position does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST hold among Rust servers?

Ranked by seven-day player hours, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST sits at #2,120 and #821 in Europe, inside the top 10%.

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

0 of 300 slots are filled on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST right now. Seven-day check: 2 players on average. Peak reading: 9. Average at the busiest hour was 2 players, at 21:00 UTC over the last 48 hours.

Operator and location

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

Its EU tag places МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST in Europe. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 37.230.137.223:27032.

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

Rust network protocol 2635 and build 168909 on Linux is the build МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs. Matching protocol is required to join. Let Steam update your game.

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

Over the last 48 hours the average was 112 server fps; the floor was 80. Peak entity count: 124,959. Buildings, deployables and all else included. Check: memory. Peak use was 4,027 MB. Lag, as players feel it, is low fps plus a climbing entity count.

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

Check: connection. МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is online at this moment. Check: restart. The uptime it reports puts the last restart about 20 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

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

Check: gather rate. The name МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST does not state one. Group size, maximum: 100 players. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Oxide plugins are running. It describes itself as vanilla. The meaning given: rates, kits and rules are exactly as Facepunch ships them. VAC is on. That is Valve's anti-cheat.

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

Size 4,500 and seed 1337: the game generates the procedural map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST from them. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.

How to join

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

Press F1 in Rust and enter client.connect 37.230.137.223:27032. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp300
Max players 300 slots in total.
ts100
Group limit You may team up with at most 100.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

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

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).

Region

EU
Europe Its browser listing: 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.