МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST
EU 37.230.137.223:27032 checked 9m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 10% of all ranked servers, top 30% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Saturday 17 October, 14:36 UTC, in 2d 16h. Its biweekly schedule tag · low confidence
- usual gap
- 1.4 days between real wipes
- on rhythm
- 33% of its recent wipes
- wipe-day peak
- 3 players, last three wipes
- crowd held
- 100% of its cycles kept half the crowd
Coming wipes
- 2d 16hSat 17 Oct, 14:36 UTC
- 16d 16hSat 31 Oct, 14:36 UTC
- 21d 21hThu 5 Nov, 19:00 UTCFW
- 30d 16hSat 14 Nov, 14:36 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 44 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 14:36 UTC 11d ago | 4 | – | running | 2 |
| Sat 3 Oct, 06:44 UTC 11d ago | 3 | – | 0.3 days | 0 |
| Thu 1 Oct, 19:58 UTCFW 13d ago | 3 | – | 1.4 days | 0 |
| Fri 18 Sep, 12:23 UTC 26d 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.
Similar servers
Quick answers
Player Numbers
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST ranking: what position does it hold?
Player hours over the last seven days place МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST at #864 in Europe, and at #2,310 in the top 10% of ranked servers.
Is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST busy?
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: 0 players now, with 300 slots available. The seven-day average player count stands at 2, and the highest point was 13. In the last 48 hours, 16:00 UTC saw the highest activity, with an average of 4 players.
Tags & Lists
How should the tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST be interpreted?
Read by the game's server browser, the tags МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST publishes are: gmrust (Game mode): Rust survival, standard; mp300 (Max players): Slot count is 300; ts100 (Group limit): 100 is the largest team allowed; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs167781 (Build): Running build 167781; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): Region code not set; ^b (Biweekly): Two-week wipe cycle; ^v (Vanilla): No changed rates, kits or rules—the game as shipped; ^o (Oxide): Uses Oxide (uMod) for plugins; EU (Europe): The server browser lists it under Europe. At the top of this page you also see its players now, its queue and when its world was made, taken from the tags.
Which lists and filters on BestRustServers.xyz contain МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
These BestRustServers.xyz lists include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: Rust servers in Europe, Rust community servers, ranked and Vanilla-tagged Rust servers. These filters on the server list display 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.
Server Overview
What Rust version is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST on?
On Linux, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs Rust network protocol 2634 and build 167781. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST smooth?
For the past 48 hours, server fps averaged 128, never dropping below 13. Buildings, deployables and the rest of the world accounted for up to 119,453 entities. Memory use peaked at 4,106 MB. What players experience as lag is low fps combined with a rising entity count.
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST uptime and reliability: what are they?
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is currently online. According to its reported uptime, the last restart was about 17 hours ago. Over the past 7 full days, it was online 168 of 168 hours, 100% of the time. It was first seen by BestRustServers.xyz on 13 September 2026.
What is the location of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
Its EU tag places МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST in Europe. BestRustServers.xyz does not look up where the machine stands; it shows where a server says it is. 37.230.137.223:27032 is its address.
Rules & Map
Which map is used on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
A procedural map of size 4,500 and seed 1337 is what МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs, generated by the game. View it on RustMaps from this page: identical size and seed produce an identical map. Called Custom Map on the map list.
What are the settings and rules for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
The name МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST carries no gather multiplier. No more than 100 players to a group. Listed as survival, gather, build, raid: the standard game. Raids and PvP are on. Under Community in the server browser, it is a community server. Plugins in use: Oxide. Vanilla is the label it uses: no changed rates, kits or rules—the game as shipped. VAC: on.
Wipe Schedule
When does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST wipe?
Its tag supplies the prediction for МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, because too few wipes are on record to confirm the schedule. Saturday 17 October at 14:36 UTC is when the next wipe is due. Its world dates from 11 days 12 hours. Its tags declare wipes every two weeks.
What happens on wipe day on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
Across its recent wipes, the busiest point averaged 3 players. 44 hours into the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 100% of its recent wipes.
Join Server
What is the process to join МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
To connect, type client.connect 37.230.137.223:27032 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you. https://m.vk.com/re_rustclub is its website.
Server tags
Published as mp300,ptrak,$r?,v2634,^b,^v,EU,gmrust,cs167781,ts100,^o
Game
gmrust- Game mode Rust survival, standard.
mp300- Max players Slot count is 300.
ts100- Group limit 100 is the largest team allowed.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs167781- Build Running build 167781.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code Region code not set.
Wipe schedule
^b- Biweekly Two-week wipe cycle.
Difficulty
^v- Vanilla No changed rates, kits or rules—the game as shipped.
Mods and access
^o- Oxide Uses Oxide (uMod) for plugins.
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.