Online 5.35.96.35:31008 checked 10m ago
RustTime | Moscow X2 02.10
Connect
srv = rust.server("5.35.96.35:31009")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
srv.rank.plot(invert=True) # 1 is best
Top 57% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its 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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 11:01 UTC17d ago | 5 | NaN | running | 1 |
| 1 | Fri 2 Oct, 14:19 UTC25d ago | 15 | halved by day 3 | 7.9 days | 0 |
| 2 | Fri 2 Oct, 05:09 UTC26d ago | 15 | NaN | 0.4 days | 0 |
| 3 | 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.
display(srv.map, srv.info())
Map
3500 · seed 347556993
- map
- Procedural Map
- size
- 3500
- seed
- 347556993
Server
srv.info()- address
- 5.35.96.35:31008
- region
- –
- max players
- 244
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 11:01 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 734 on average | 630/600 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 548 on average | 412/375 |
| 2 | Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 354 on average | 129/150 |
| 3 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 326 on average | 134/150 |
| 4 | Magic Rust #18 — Vanilla 2x | Pyccкий | EU · groups of 150+ · 2x · weekly · 323 on average | 44/100 |
| 5 | MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 299 on average | 203/1000 |
Quick answers
From the figures on this page.
Population
What position does RustTime | Moscow X2 02.10 take in the server rankings?
Over the last seven days RustTime | Moscow X2 02.10 sits at #12,570 on player hours, in the top 57% of ranked servers.
What population does RustTime | Moscow X2 02.10 carry?
Current row: 0 players on RustTime | Moscow X2 02.10, against 244 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 05:00 UTC, mean 0 players.
About the server
How smoothly does RustTime | Moscow X2 02.10 run?
The 48-hour average is 162 server fps, with a low of 98. Buildings, deployables and all else in the world took the count as high as 69,913 entities. Memory peaked at 2,738 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does RustTime | Moscow X2 02.10 run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by RustTime | Moscow X2 02.10. The protocol has to match before you can join, and Steam does the updating.
How reliable is RustTime | Moscow X2 02.10, and is it up?
RustTime | Moscow X2 02.10 reports itself online at the current refresh. Count back 2 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 13 September 2026.
Where does RustTime | Moscow X2 02.10 sit?
There is no region published for RustTime | Moscow X2 02.10. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 5.35.96.35:31008 is its address.
Map and rules
Which settings and rules does RustTime | Moscow X2 02.10 run?
The name carries the figure: RustTime | Moscow X2 02.10 runs 2x gather. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has RustTime | Moscow X2 02.10 loaded?
Size 3,500, seed 347556993: the procedural map on RustTime | Moscow X2 02.10, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does RustTime | Moscow X2 02.10 wipe, and on what schedule?
No next wipe can be predicted for RustTime | Moscow X2 02.10, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 17 days 21 hours ago.
What is wipe day on RustTime | Moscow X2 02.10 like?
The average peak over recent wipes is 12 players. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 50% of recent wipes. Otherwise the crowd fell below half by day 3.
Lists and tags
Which Rust Data filters and lists contain RustTime | Moscow X2 02.10?
These Rust Data lists include RustTime | Moscow X2 02.10: Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.
Which meanings do the tags on RustTime | Moscow X2 02.10 hold?
The game's server browser reads these tags from RustTime | Moscow X2 02.10: gmrust (Game mode): Survival play, standard Rust; mp244 (Max players): 244 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to RustTime | Moscow X2 02.10?
The manual route: launch Rust, F1, then client.connect 5.35.96.35:31008. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://rusttimes.gamestores.app/.
