RustTime | Moscow X2 02.10
Online 5.35.96.35:31008 checked 10m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 57% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on RustTime | Moscow X2 02.10?
The average peak across its recent wipes is 12 players. The crowd on the latest wipe reached its peak 0 hours in. Above half the peak until the next wipe: that held in 50% of its recent wipes. It fell below half by day 3 when it did not hold.
What is the wipe schedule on RustTime | Moscow X2 02.10?
Wipes come at irregular times on RustTime | Moscow X2 02.10, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world it runs now dates from 17 days 23 hours ago.
Player counts
How busy is RustTime | Moscow X2 02.10?
The current population of RustTime | Moscow X2 02.10 is 0, against 244 slots. The average across the last seven days is 0 players; the peak reached 1. Its busiest point in the last 48 hours was 05:00 UTC, averaging 0 players.
How does RustTime | Moscow X2 02.10 rank against other Rust servers?
The top 57% of ranked servers includes RustTime | Moscow X2 02.10, at #12,575 for player hours over the last seven days.
Rules and settings
Which map does RustTime | Moscow X2 02.10 run?
A procedural map of size 3,500 with seed 347556993, generated by the game, runs on RustTime | Moscow X2 02.10. The map is the same for a given size and seed, so RustMaps can show it from this page.
What are the rules and settings on RustTime | Moscow X2 02.10?
2x gather is what RustTime | Moscow X2 02.10 advertises in its name. The group limit is 8 players, which is the game's default. survival is the game mode, standard play: gathering, building and raiding. Combat between players and raiding are both possible. Plugins or settings change the game, and it is listed under Modded in the server browser. Plugin count: Carbon. Anti-cheat: Valve's VAC is on.
Location and uptime
Which version of Rust does RustTime | Moscow X2 02.10 run?
The build on RustTime | Moscow X2 02.10 is Rust network protocol 2635 and build 168909, running on Linux. Your game must run the same protocol to join, and Steam takes care of updating it.
Is RustTime | Moscow X2 02.10 online, and how reliable is it?
The server is up at the moment: RustTime | Moscow X2 02.10 is online. Its reported uptime dates the last restart to about 3 hours ago. 168 of 168 hours up over the last 7 full days, which is 100%. It first appears in Rust Heatmap records on 13 September 2026.
Where is RustTime | Moscow X2 02.10 located?
Nothing about a region comes from RustTime | Moscow X2 02.10. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 5.35.96.35:31008 is its address.
Does RustTime | Moscow X2 02.10 run smoothly?
Average server fps over the last 48 hours was 161; it never dropped below 98. Entities peaked at 69,749, counting buildings, deployables and all the rest of the world. The highest memory use was 2,738 MB. What players call lag is low fps together with a growing entity count.
Lists and filters
Which Rust Heatmap lists and filters include RustTime | Moscow X2 02.10?
These Rust Heatmap lists include RustTime | Moscow X2 02.10: 2x Rust servers and Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x brings it up.
What do the server tags on RustTime | Moscow X2 02.10 mean?
gmrust (Game mode): Survival in the standard Rust form; mp244 (Max players): Slot count: 244; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^z (Modded): Listed as Modded, since settings or plugins change the game; ^y (Carbon): Carbon provides the plugin framework here are the tags RustTime | Moscow X2 02.10 publishes, and the server browser reads them. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
How to join
How do I join RustTime | Moscow X2 02.10?
To join by console, open it with F1 in Rust and enter client.connect 5.35.96.35:31008. Or press Launch Rust on this page, which connects you through Steam. You can find it online at https://rusttimes.gamestores.app/.