Rust Player Count
36,021 playing now

Offline5.35.96.35:31008checked 1d ago

RustTime | Moscow X2 02.10

2x moddedcarbon
Players now 1/ 244 0% full
7-day average 1 peak 5
Rank #4,415 top 20%
Last wipe 3d ago no schedule published
Next wipe – no rhythm it keeps

Players

AveragePeak
00.250.50.75108:0012:0016:0021:0001:0005:00

Hourly average and peak, UTC.

Server performance

05010015020008:0012:0016:0021:0001:0005:00

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
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

Top 20% of all ranked servers. Ranked on player hours over the last seven days.

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 gap 6.6 days between real wipes
On rhythm 33% of its recent wipes
Wipe-day peak 12 players, last three wipes
Crowd held 50% else halves by day 3

The first 48 hours of its last wipes

Sat 10 OctFri 2 OctFri 2 Oct
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 0 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 11:01 UTC3d ago 5 – running 1
Fri 2 Oct, 14:19 UTC11d ago 15 halved by day 3 7.9 days 0
Fri 2 Oct, 05:09 UTC12d ago 15 – 0.4 days 0
Fri 25 Sep, 14:23 UTC18d 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
Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 643 on average 208/ 250
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 419 on average 101/ 100
MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10EU · groups of 300+ · 2x · monthly · 301 on average 137/ 500
MIRAGE RUST | MAIN 2x | VANILLA+ | Wipe 09.10EU · groups of 300+ · 2x · weekly · 293 on average 12/ 1000
Magic Rust #18 — Vanilla 2x | PyccкийEU · groups of 150+ · 2x · weekly · 260 on average 7/ 100
Magic Rust #27 — Vanilla 2x (Monthly) | PyccкийEU · groups of 150+ · 2x · monthly · 255 on average 91/ 300

Quick answers

from the figures on this page

Rules, map and settings

Which rules govern RustTime | Moscow X2 02.10?

RustTime | Moscow X2 02.10 sets its gather rate to 2x, as its name states. Up to 8 players per group, which is the game's default. survival is the game mode, gather, build, raid: the standard game. You can fight and raid other players. The server browser lists it as Modded, with plugins or settings that alter the game. Carbon plugins are running on it. Anti-cheat VAC from Valve is on.

What map is used on RustTime | Moscow X2 02.10?

RustTime | Moscow X2 02.10 runs a procedural map of size 3,500 with seed 347556993, generated by the game. The map is identical for the same size and seed, so it can be viewed on RustMaps from this page.

Tags, lists and filters

Where can RustTime | Moscow X2 02.10 be found in Rust Player Count lists and filters?

These Rust Player Count lists include RustTime | Moscow X2 02.10: Rust servers with a 2x gather rate and Modded 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; Last wipe: In the last week; Gather rate: 2x.

How should you interpret the tags on RustTime | Moscow X2 02.10?

These are the tags RustTime | Moscow X2 02.10 publishes for the game's server browser: gmrust (Game mode): Survival as standard in Rust; mp244 (Max players): The server has 244 slots; ts8 (Group limit): This uses the default team cap: 8 players; v2634 (Protocol): To join, your game must match protocol 2634; cs167398 (Build): It runs on game build 167398; ptrak (Networking): RakNet is the game's usual network protocol, and this server uses it; $r? (Region code): No region code is set; ^z (Modded): The Modded category: plugins or configuration change gameplay; ^y (Carbon): It uses Carbon for plugins. The tags also include its current players, its queue and when its world was made, shown at the top of this page.

Player count

What is the player count on RustTime | Moscow X2 02.10?

Currently offline, RustTime | Moscow X2 02.10 was last seen 26 hours ago. The seven-day average is 1 players, with a peak of 5. The highest average in the last 48 hours was 1 players at 05:00 UTC.

How does RustTime | Moscow X2 02.10 compare in server rankings?

RustTime | Moscow X2 02.10 is in the top 20% of all ranked servers with a rank of #4,415 for player hours over the past seven days.

Server information

How reliable is RustTime | Moscow X2 02.10, and is it online?

RustTime | Moscow X2 02.10 is down at the moment and was last seen 26 hours ago. Based on the uptime it reports, the last restart was about 23 hours ago. For the last 7 full days, it was online for 106 of 168 hours, a 63% uptime. Its first appearance in Rust Player Count was on 13 September 2026.

What Rust version is used on RustTime | Moscow X2 02.10?

Rust network protocol 2634 and build 167398 on Linux is what RustTime | Moscow X2 02.10 uses. The protocol has to match for you to join, but Steam updates it without any action from you.

Where can you find RustTime | Moscow X2 02.10?

A region is not published by RustTime | Moscow X2 02.10. Rust Player Count displays the location a server claims, not the physical location of the machine. You can reach it at 5.35.96.35:31008.

Is RustTime | Moscow X2 02.10 lag-free?

Over the last 48 hours, the average server fps was 140, and it never dropped below 99. Up to 70,179 entities were present, including buildings, deployables and other world objects. Peak memory use was 2,551 MB. Lag, as players experience it, is caused by low fps and increasing entities.

Wipe schedule

What happens on RustTime | Moscow X2 02.10 when a wipe occurs?

Recent wipes saw an average peak of 12 players. 0 hours after the wipe, the crowd on the latest wipe was at its highest. Half that peak was maintained until the next wipe in 50% of recent wipes. If not, the crowd went below half by day 3.

How often does RustTime | Moscow X2 02.10 wipe?

No next wipe can be predicted for RustTime | Moscow X2 02.10, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe arrives, wiping every Rust server. It has been running its current world for 3 days 20 hours.

Connect to the server

What steps are needed to join RustTime | Moscow X2 02.10?

To get in, press F1 in Rust and enter client.connect 5.35.96.35:31008. You can also click Launch Rust here, which opens the game through Steam and brings you onto the server. You can find its website at https://rusttimes.gamestores.app/.

Server tags

what each one means

Published as mp244,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y

Game

gmrust
Game mode Survival as standard in Rust.
mp244
Max players The server has 244 slots.
ts8
Group limit This uses the default team cap: 8 players.
v2634
Protocol To join, your game must match protocol 2634.
cs167398
Build It runs on game build 167398.
ptrak
Networking RakNet is the game's usual network protocol, and this server uses it.
$r?
Region code No region code is set.

Mods and access

^z
Modded The Modded category: plugins or configuration change gameplay.
^y
Carbon It uses Carbon for plugins.

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.