On the class lists: D (53), with population over 48 hours and no performance mark.
Players now3/ 1003% full
7-day average1peak 12
Rank#2,644top 12%
Last wipe5h agono schedule published
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
88/ 100
A−
Holds a respectable place: #2,644 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 79 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
47/ 100
D
Slipped a little: down 185 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 12% of all ranked servers. 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
a steady gap
Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h.
The force wipe · high confidence
usual gap13.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak8players, last three wipes
crowd held33%else halves by day 7
Coming wipes
7d 3hThu 5 Nov, 19:00 UTCFW
13d 15hThu 12 Nov, 06:53 UTC
27d 12hThu 26 Nov, 03:42 UTC
35d 3hThu 3 Dec, 19:00 UTCFW
41d 9hThu 10 Dec, 00:31 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctWed 16 Sep
Players each hour, from the hour of the wipe. The latest peaked at 6, 23 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 10:04 UTC5h ago
–
–
running
2
Thu 15 Oct, 13:15 UTC14d ago
6
–
–
5
Thu 1 Oct, 19:52 UTCFW27d ago
6
halved by day 7
13.7 days
0
Wed 16 Sep, 16:32 UTC42d ago
11
halved by day 7
15.1 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 Moscow | X1 | Для новичков | 29.10.2026 based in?
The name of Moscow | X1 | Для новичков | 29.10.2026 points to Europe, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 37.230.162.180:28015 is the address to use.
Is Moscow | X1 | Для новичков | 29.10.2026 up, and how steady is its uptime?
The server is up: Moscow | X1 | Для новичков | 29.10.2026 is online now. The uptime it reports puts the last restart at about 3 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does Moscow | X1 | Для новичков | 29.10.2026 run?
It never fell below 42 server fps in the last 48 hours, averaging 79. Buildings, deployables and everything else in the world added up to as many as 149,009 entities. At its highest, it used 4,715 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Moscow | X1 | Для новичков | 29.10.2026 running?
Rust network protocol 2635 and build 168909 on Linux is what Moscow | X1 | Для новичков | 29.10.2026 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Moscow | X1 | Для новичков | 29.10.2026 reset?
The gap between Moscow | X1 | Для новичков | 29.10.2026's wipes has been about 13.9 days recently. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 5 hours.
What happens on Moscow | X1 | Для новичков | 29.10.2026 when wipe day arrives?
Across its recent wipes, the busiest moments averaged 8 players. 23 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 33% of its recent wipes. The crowd dropped below half by day 7 in the wipes where it did not hold.
Player numbers
What position does Moscow | X1 | Для новичков | 29.10.2026 hold in the rankings?
In the top 12% of all ranked servers, Moscow | X1 | Для новичков | 29.10.2026 sits at #2,644 for player hours over the last seven days.
What does the population on Moscow | X1 | Для новичков | 29.10.2026 look like?
With 100 slots available, Moscow | X1 | Для новичков | 29.10.2026 currently has 3 players. The seven-day average is 1 players, with a peak of 12. The highest average in the last 48 hours came at 12:00 UTC, with 4 players.
Lists and filters
How should you read the tags on Moscow | X1 | Для новичков | 29.10.2026?
You'll see Moscow | X1 | Для новичков | 29.10.2026 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; jp0 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner 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 Moscow | X1 | Для новичков | 29.10.2026?
Rust Server Score lists that include Moscow | X1 | Для новичков | 29.10.2026: European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours; Gather rate: 1x.
Rules and settings
What settings and rules apply on Moscow | X1 | Для новичков | 29.10.2026?
The name of Moscow | X1 | Для новичков | 29.10.2026 points to a 1x gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Moscow | X1 | Для новичков | 29.10.2026 uses?
The game generates the procedural map on Moscow | X1 | Для новичков | 29.10.2026 at size 3,700 with seed 38461994. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How should you connect to Moscow | X1 | Для новичков | 29.10.2026?
Enter client.connect 37.230.162.180:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://rustmoscow.gamestores.app.
Server tags
what each one means
Published asmp100,ptrak,jp0,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Other
jp0
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).