Skip to the page
Network live 11,810 servers online 83,965 players aboard 336 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

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

Online EU 37.230.137.223:27032 checked 12m ago

biweekly wipes vanillaoxide
Tracking number · connect
Launch Rust and join
Wipe progress · wiped 13d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Fri 30 Oct, 11:10 UK Fri 30 Oct, 11:10 UTC in 13h · low confidence
2/ 300 players now 1% full
27-day averagepeak 9
#2,124ranktop 10% · #817 in EU
13d agolast wipebiweekly schedule
13hnext wipeFri 30 Oct, 11:10 UTC
Delivery history

Players, performance and rank

Players

AveragePeak
0123423:0008:0017:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

05010015020023:0008:0017:0002:0011:0020: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.

Rank

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

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

Wipe schedule

from its schedule tag
Next delivery expected

Next wipe Friday 30 October, 11:10 UTC · 11:10 UK, in 13h.

Its biweekly schedule tag · low confidence
7.2 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
4wipe-day peakplayers, last three wipes
100%crowd heldof its cycles kept half the crowd

Coming wipes

  1. 13hFri 30 Oct, 11:10 UTC11:10 UK
  2. 6d 20hThu 5 Nov, 19:00 UTC19:00 UKFW
  3. 14d 13hFri 13 Nov, 11:10 UTC11:10 UK
  4. 28d 13hFri 27 Nov, 11:10 UTC11:10 UK
  5. 34d 20hThu 3 Dec, 19:00 UTC19:00 UKFW
  6. 42d 13hFri 11 Dec, 11:10 UTC11:10 UK

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.

Wipes

every wipe as a delivery, newest first
  1. Fri 30 Oct, 11:10 UTC11:10 UK · in 13h
    Next wipe expected · its biweekly schedule tag
  2. Fri 16 Oct, 11:10 UTC 12:10 UK · 13d ago
    Wipe delivered
    Peak
    6
    Crowd
    –
    Lasted
    running
    Players before
    0
  3. Sat 3 Oct, 14:36 UTC 15:36 UK · 26d ago
    Wipe delivered
    Peak
    4
    Crowd
    held half
    Lasted
    12.9 days
    Players before
    2
  4. Sat 3 Oct, 06:44 UTC 07:44 UK · 26d ago
    Wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    0.3 days
    Players before
    0
  5. Thu 1 Oct, 19:58 UTC FW 20:58 UK · 28d ago
    Force wipe delivered
    Peak
    3
    Crowd
    –
    Lasted
    1.4 days
    Players before
    0
  6. Fri 18 Sep, 12:23 UTC 13:23 UK · 41d ago
    Wipe delivered
    Peak
    2
    Crowd
    held half
    Lasted
    13.3 days
    Players before
    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.

Similar parcels

Similar servers

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

  1. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 242 on average 635 / 725
  2. Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 130 on average 503 / 750
  3. Rusty Moose |EU Biweekly|EU · groups of 12+ · biweekly · 49 on average 588 / 650
  4. Rustoria.co - EU MediumEU · groups of 12+ · biweekly · 34 on average 375 / 425
  5. Rustopia.gg - EU MediumEU · groups of 12+ · biweekly · 30 on average 366 / 475
  6. Rustafied.com - EU Medium - SmallEU · groups of 16+ · biweekly · 19 on average 258 / 300
Help desk

Quick answers

From the figures on this page.

Player activity

Where does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST place among Rust servers?

Ranked #2,124 on player hours over the last seven days, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is #817 in Europe and in the top 10% of all ranked servers.

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

At the moment 2 players are on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, which has 300 slots. Averaged over the past week: 2 players, peaking at 9. Over the last 48 hours, the peak hour came at 13:00 UTC with an average of 2 players.

Rules and settings

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

Size 4,500 and seed 1337 define the procedural map МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs, generated by the game. Identical size and seed give an identical map: view it on RustMaps from this page. You will see this map name: Custom Map.

What are the rules on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and what settings does it run?

No gather rate appears in the name of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. The group limit is 100 players. It runs survival, the usual game: build, gather, raid. You can raid and fight other players. The server browser files it under Community, as a community server. Oxide supplies the plugins. Vanilla is the label it uses for itself: no altered rates, kits or rules: the game as shipped by Facepunch. VAC, Valve's anti-cheat, is switched on.

Operator and location

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

With its EU tag, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST places itself in Europe. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. 37.230.137.223:27032 is its address.

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

Server fps over the last 48 hours averaged 112; the lowest was 80. The world held as many as 125,337 entities: buildings, deployables and the rest. 4,027 MB of memory was its top figure. Lag, to players, means low fps alongside an entity count on the rise.

What is the uptime of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and is it online?

You can find МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST online at present. The uptime it reports puts its last restart at about 17 hours ago. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 13 September 2026.

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

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

Map resets

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

At their busiest, its recent wipes drew an average of 4 players. After 29 hours the latest wipe's crowd hit its peak. Until the next wipe, the crowd stayed over half the peak in 100% of recent cases.

When does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST wipe? What schedule does it follow?

The prediction is taken from its tag, as МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST has too few wipes on record to confirm the schedule. Due on Friday 30 October at 11:10 UTC: its next wipe. You are playing a world created 13 days 10 hours. Its tags give the wipe schedule as every two weeks.

Server tags

Where does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST appear across the Rust Wipe Tracker lists and filters?

The Rust Wipe Tracker lists that include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST are: Rust servers in Europe, Rust community servers, unmodded and Vanilla Rust servers. On the server list, apply 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 and it appears.

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

gmrust (Game mode): Survival in standard Rust; mp300 (Max players): The server has 300 slots; ts100 (Group limit): Teams are limited to 100 players; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): The region code is unset; ^b (Biweekly): A wipe comes every fortnight; ^v (Vanilla): No altered rates, kits or rules: the game as shipped by Facepunch; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; EU (Europe): In the server browser it appears under Europe are the tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Connecting

What steps do you take to join МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 37.230.137.223:27032.

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.
mp300
Max players The server has 300 slots.
ts100
Group limit Teams are limited to 100 players.
v2635
Protocol Join only if your game runs protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly A wipe comes every fortnight.

Difficulty

^v
Vanilla No altered rates, kits or rules: the game as shipped by Facepunch.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed 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.