Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO K SRV11,859online PAX101,852playing OCC3,917with players WIPED 3H538
VANVanilla traffic
Callsign

BWK2126=

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

Online EU 37.230.137.223:27032 checked 8m ago

biweekly wipes vanillaoxide
Clearance · join
Players now 2/ 300 1% full
7-day average2peak 9
Rank#2,126top 10% · #819 in EU
Last wipe13d agobiweekly schedule
Next wipe15hFri 30 Oct, 11:10 UTC
Track history

Players

AveragePeak
0123421:0006:0015:0000:0009:0018:00

Hourly average and peak, UTC.

Server performance

05010015020021:0006:0015:0000:0009:0018: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.

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Friday 30 October, 11:10 UTC, in 15h.

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

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.

Nearby traffic

Similar servers

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

  1. 01COM
    Callsign RST015EU · groups of 12+ · biweekly · 240 on average Rustoria.co - EU East Medium
    Players 780/800
  2. 02COM
    Callsign RST018EU · groups of 16+ · biweekly · 128 on average Rustafied.com - EU Medium - Large
    Players 617/750
  3. 03COM
    Callsign RST015EU · groups of 12+ · biweekly · 44 on average Rusty Moose |EU Biweekly|
    Players 725/800
  4. 04COM
    Callsign RST015EU · groups of 12+ · biweekly · 32 on average Rustoria.co - EU Medium
    Players 490/525
  5. 05COM
    Callsign RST010EU · groups of 12+ · biweekly · 27 on average Rustopia.gg - EU Medium
    Players 529/600
  6. 06COM
    Callsign RST018EU · groups of 16+ · biweekly · 17 on average Rustafied.com - EU Medium - Small
    Players 287/300
ATIS · this server

Quick answers

From the figures on this page.

Tags

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

EU Rust servers, tracked live, Community servers, no tags and Vanilla Rust servers, tracked live — the Rust Tracker lists that include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST. These filters surface it 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 should you read the tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

These tags are published by МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp300 (Max players): Capacity: 300 slots; ts100 (Group limit): Teams are capped at 100; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): Region code: not set; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): As Facepunch ships it: rates, kits and rules are unchanged; ^o (Oxide): Plugin framework: Oxide (uMod); EU (Europe): The server browser lists it under Europe. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

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

At their busiest, recent wipes averaged 4 players. The peak on the latest wipe came 29 hours after it. Half the peak was held until the next wipe in 100% of its recent wipes.

Which wipe times are confirmed for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?

The schedule of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST cannot be confirmed, with too few wipes on record: the prediction follows its tag. Friday 30 October at 11:10 UTC is when the next wipe falls due. This world has been running 13 days 8 hours. Tags list a wipe schedule of every two weeks.

Server Details

Is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST up, and how does its uptime hold?

Tracking shows МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST online as of now. The uptime it reports puts the last restart about 15 hours ago. 99% uptime over the last 7 full days, with 167 of 168 hours up. The first sighting by Rust Tracker was 13 September 2026.

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

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

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

Average server fps over the last 48 hours: 112, with a low of 80. Peak entity count: 125,434, covering buildings, deployables and all else in the world. It drew as much as 4,069 MB of memory. Players feel lag when fps drops and the entity count climbs.

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

The EU tag places МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST in Europe, by its own listing. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 37.230.137.223:27032.

Player Count

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

Tracking МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: 2 of 300 slots filled. Seven-day average 2 players; peak 9. Peak traffic in the last 48 hours came at 21:00 UTC, averaging 2 players.

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

Top 10% of all ranked servers and #819 in Europe: МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST ranks #2,126 on player hours over the last seven days.

Settings

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

Nothing in МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's name states a gather rate. The group limit is 100 players. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Community, as a community server. Oxide plugins run on it. Vanilla is its own label: as Facepunch ships it: rates, kits and rules are unchanged. On: VAC, Valve's anti-cheat.

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

The map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is procedural, size 4,500, seed 1337, generated by the game. Look at it on RustMaps from this page: equal size and seed return the same map. Its map goes by the name Custom Map.

Connect

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

To connect: start Rust, press F1, enter client.connect 37.230.137.223:27032 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp300
Max players Capacity: 300 slots.
ts100
Group limit Teams are capped at 100.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer: RakNet, the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Difficulty

^v
Vanilla As Facepunch ships it: rates, kits and rules are unchanged.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

Region

EU
Europe The server browser lists it 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.