RustTime | Moscow X2 02.10
Online 5.35.96.35:31008 checked 14m ago
Server instruments
last reading Tue 23:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 98 · below 20 is lag, below 10 is badEntities
48 h range 57,264–69,913 · memory 2,185 MBUptime
18 h 4 min since its last restart, at the last readingPlayers
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
daily · 1 is bestTop 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
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 UTC17d 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 UTC25d 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
the same kind of game, then region, group limit, rate and wipes- 383/450
- 220/275
- 204/250
- 98/150
- 8/100
- 124/1000
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on RustTime | Moscow X2 02.10?
An average of 12 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. When it didn't hold, by day 3 it fell below half.
When does RustTime | Moscow X2 02.10 wipe?
No next wipe can be predicted for RustTime | Moscow X2 02.10, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 17 days 14 hours ago.
Tag meanings
How should you read the tags on RustTime | Moscow X2 02.10?
These are the tags RustTime | Moscow X2 02.10 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp244 (Max players): 244 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. Carbon. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show RustTime | Moscow X2 02.10?
These Rust Metrics lists carry RustTime | Moscow X2 02.10: 2x Rust servers, checked live and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.
Population
Where does RustTime | Moscow X2 02.10 sit in the rankings?
Player hours over seven days put RustTime | Moscow X2 02.10 at #14,287, in the top 64% of all ranked servers.
What player count does RustTime | Moscow X2 02.10 carry?
0 of 244 slots are filled on RustTime | Moscow X2 02.10 right now. Check: players over seven days. Average 0, peak 1.
Operator and location
What location is RustTime | Moscow X2 02.10 hosted in?
No region tag on RustTime | Moscow X2 02.10. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 5.35.96.35:31008.
What Rust version is RustTime | Moscow X2 02.10 on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by RustTime | Moscow X2 02.10. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for RustTime | Moscow X2 02.10?
Check: fps. Average 165 server fps over the last 48 hours, low of 98. Within range. Peak entity count: 69,913. Buildings, deployables and all else included. Reading: 2,738 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
Is RustTime | Moscow X2 02.10 up, and how often does it stay up?
RustTime | Moscow X2 02.10 reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 18 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
How is RustTime | Moscow X2 02.10 configured, and what rules are in force?
Gather rate check: 2x. That comes from the name RustTime | Moscow X2 02.10. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.
What map is RustTime | Moscow X2 02.10 on?
Check: map. Procedural, size 3,500, seed 347556993, generated by the game on RustTime | Moscow X2 02.10. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How can you get onto RustTime | Moscow X2 02.10?
Check: join. Open Rust, press F1, then enter client.connect 5.35.96.35:31008. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://rusttimes.gamestores.app/.