On the class lists: D (50), with population over 48 hours and no performance mark.
Players now0/ 2440% full
7-day average0peak 1
Rank#12,606top 57%
Last wipe18d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 244 on average. Plenty of space to grow.
Standingrank on player hours
43/ 100
F
Working its way up from the back of the class: #12,606 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 162 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
58/ 100
C−
Moving up: up 2,075 places this week.
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.
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 57% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
·····W·
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap6.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak12players, last three wipes
crowd held50%else halves by day 3
The first 48 hours of its last wipes
Sat 10 OctFri 2 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 5, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 11:01 UTC18d ago
5
–
running
1
Fri 2 Oct, 14:19 UTC25d ago
15
halved by day 3
7.9 days
0
Fri 2 Oct, 05:09 UTC26d ago
15
–
0.4 days
0
Fri 25 Sep, 14:23 UTC32d ago
9
✓ held half
6.6 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
EU · groups of 300+ · 2x · weekly · 303 on average
329 / 1000
Quick answers
from the figures on this page
About the server
In what location does RustTime | Moscow X2 02.10 sit?
No region is published for RustTime | Moscow X2 02.10. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 5.35.96.35:31008.
How dependable is RustTime | Moscow X2 02.10, and is it online at the moment?
Right now, RustTime | Moscow X2 02.10 is online. The uptime it reports puts the last restart at about 6 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
How well does RustTime | Moscow X2 02.10 run?
It never fell below 98 server fps in the last 48 hours, averaging 162. Up to 69,747 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 2,738 MB of memory. When fps is low and entities climb, that is lag to players.
Which Rust version is RustTime | Moscow X2 02.10 running?
You will find RustTime | Moscow X2 02.10 on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does RustTime | Moscow X2 02.10 reset?
There is no next wipe to predict on RustTime | Moscow X2 02.10, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 18 days 1 hours have passed since this world was made.
What should you expect from wipe day on RustTime | Moscow X2 02.10?
Recent wipes have peaked at 12 players on average. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Population
Where does RustTime | Moscow X2 02.10 sit among Rust servers?
In the top 57% of all ranked servers, RustTime | Moscow X2 02.10 sits at #12,606 for player hours over the last seven days.
How many players does RustTime | Moscow X2 02.10 usually have?
Right now, 0 players are on RustTime | Moscow X2 02.10, which has 244 slots. The seven-day average is 0 players, with a peak of 1. The busiest time in the last 48 hours was 05:00 UTC, with an average of 0 players.
Tags and filters
What is meant by the tags on RustTime | Moscow X2 02.10?
gmrust (Game mode): Survival in the standard Rust style; mp244 (Max players): Its slot count is 244; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags RustTime | Moscow X2 02.10 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature RustTime | Moscow X2 02.10?
Rust Server Score lists that include RustTime | Moscow X2 02.10: 2x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.
Map and rules
What settings and rules apply on RustTime | Moscow X2 02.10?
The name of RustTime | Moscow X2 02.10 points to a 2x gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Which map is in play on RustTime | Moscow X2 02.10?
The game generates the procedural map on RustTime | Moscow X2 02.10 at size 3,500 with seed 347556993. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to RustTime | Moscow X2 02.10?
Enter client.connect 5.35.96.35:31008 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://rusttimes.gamestores.app/.
Server tags
what each one means
Published asmp244,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp244
Max playersIts slot count is 244.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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).