On the class lists: C+ (66), with population over 48 hours and no performance mark.
Players now2/ 3001% full
7-day average2peak 9
Rank#2,124top 10% · #817 in EU
Last wipe13d agobiweekly schedule
Next wipe13hFri 30 Oct, 11:10 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 2 of 300 on average. Plenty of space to grow.
Standingrank on player hours
90/ 100
A
Well up the rankings: #2,124 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 112 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 182 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
Top 10% of all ranked servers, top 28% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
···F·W·
·······
····W··
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 11:10 UTC, in 13h.
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
13hFri 30 Oct, 11:10 UTC
6d 21hThu 5 Nov, 19:00 UTCFW
14d 13hFri 13 Nov, 11:10 UTC
28d 13hFri 27 Nov, 11:10 UTC
34d 21hThu 3 Dec, 19:00 UTCFW
42d 13hFri 11 Dec, 11:10 UTC
The first 48 hours of its last wipes
Fri 16 OctSat 3 OctSat 3 Oct
Players each hour, from the hour of the wipe. The latest peaked at 6, 29 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 UTCFW28d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST based in?
The EU tag on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 37.230.137.223:27032.
How reliable is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST, and is it up?
You can join now: МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is online. About 17 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
How well does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST run?
It averaged 112 server fps over the last 48 hours, with a low of 80. Up to 125,434 entities were in the world, covering buildings, deployables and the rest. Up to 4,027 MB of memory was used. Players feel lag when fps drops and entities pile up.
Which Rust version is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST running?
The server МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is on Rust network protocol 2635 and build 168909 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST reset?
Its tag sets the prediction, as the record holds too few of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST's wipes to confirm its schedule. Friday 30 October at 11:10 UTC is the date set for its next wipe. 13 days 10 hours have passed since this world was made. Its tags say it wipes every two weeks.
What should you expect from wipe day on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
Recent wipes have peaked at 4 players on average. 29 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 100% of its recent wipes.
Population
Where does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST place in the wider field of Rust servers?
In Europe, МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is #817, and overall it is #2,124 on player hours over the last seven days, in the top 10% of all ranked servers.
How many players does МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST usually have?
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST is showing 2 players right now, with 300 slots in total. The seven-day average is 2 players, with a peak of 9. The highest average in the last 48 hours came at 13:00 UTC, with 2 players.
Lists and filters
What is meant by the tags on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
You'll see МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp300 (Max players): 300 slots are available; ts100 (Group limit): A team can hold 100 players at most; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); EU (Europe): The server browser lists it under Europe in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
Rust Server Score lists that include МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST: European Rust servers, graded, Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: 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.
Rules and settings
How is МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST set up, and what rules does it keep?
Nothing in the name of МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST states a gather rate. The limit for a group is 100 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. Oxide plugins are running on it. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST runs which map?
The game generates the procedural map on МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST at size 4,500 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Getting in
How do you get onto МОСКОВСКИЙ КЛАССИКА / BEWEEKLY / RE:RUST?
To connect, start Rust, press F1, and type client.connect 37.230.137.223:27032. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp300,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts100,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp300
Max players300 slots are available.
ts100
Group limitA team can hold 100 players at most.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
EU
EuropeThe 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.
A steady term. Strongest in performance (A+); population is the one to work on (F).