RUST ZERG LIFEClan war room · live
No limit8 · game default
Deployment dossierOffline

RustTime | Moscow X2 02.10

5.35.96.35:31008 checked 1d ago

2x moddedcarbon
Deploy
Zerg meter0%light
1/244 troops
7-day average1
peak 5
Rank#4,452
top 20%
Last wipe3d ago
no schedule published
Next wipe · H-hour–
no rhythm it keeps

Players

AveragePeak
00.250.50.75110:0014:0018:0021:0001:0005:00

Hourly average and peak, UTC.

Server performance

05010015020010:0014:0018: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 gap6.6 days
between real wipes
on rhythm33%
of its recent wipes
wipe-day peak12
players, 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
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
Zergmax 16
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 640 on average
302/350
Zergmax 16
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 417 on average
169/175
Zergmax 300
MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 EU · groups of 300+ · 2x · monthly · 300 on average
189/500
Zergmax 300
MIRAGE RUST | MAIN 2x | VANILLA+ | Wipe 09.10 EU · groups of 300+ · 2x · weekly · 293 on average
21/1000
Zergmax 150
Magic Rust #18 — Vanilla 2x | Pyccкий EU · groups of 150+ · 2x · weekly · 260 on average
16/100
Zergmax 150
Magic Rust #27 — Vanilla 2x (Monthly) | Pyccкий EU · groups of 150+ · 2x · monthly · 253 on average
143/300

Quick answers

from the figures on this page

Map and rules

What settings does RustTime | Moscow X2 02.10 run?

Its name says 2x gather, and that is what RustTime | Moscow X2 02.10 runs. The group cap is 8 players, the default for the game. survival is the game mode, gather, build and raid: the standard game. Raiding and fighting other players are allowed. This one sits under Modded in the browser: the game is changed by plugins or settings. Carbon plugins are running on it. VAC is on, Valve's anti-cheat.

What is the map on RustTime | Moscow X2 02.10?

Size 3,500, seed 347556993, generated by the game: the procedural map on RustTime | Moscow X2 02.10. You can view it on RustMaps from this page, since the same size and seed give the same map.

Population

How many players are on RustTime | Moscow X2 02.10?

The server RustTime | Moscow X2 02.10 is currently offline; it was last seen 28 hours ago. The seven-day average is 1 players, with a peak of 5. The highest average over the last 48 hours came at 05:00 UTC, with 1 players.

Where does RustTime | Moscow X2 02.10 sit in the rankings?

For player hours over the last week, RustTime | Moscow X2 02.10 is #4,452, which puts it in the top 20% of all ranked servers.

Server tags

What is the meaning of the tags on RustTime | Moscow X2 02.10?

For the game's server browser, RustTime | Moscow X2 02.10 publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp244 (Max players): Capacity: 244; ts8 (Group limit): Teams max out at 8—the default setting for Rust; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): There's no region code here; ^z (Modded): The Modded listing means plugins or settings have changed the game; ^y (Carbon): Carbon plugin framework is running. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.

Which Rust Zerg Life filters and lists cover RustTime | Moscow X2 02.10?

The Rust Zerg Life lists that include RustTime | Moscow X2 02.10 are 2x Rust servers for clans and zergs and Modded Rust servers for clans and zergs. Under these filters it shows 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.

About the server

Is RustTime | Moscow X2 02.10 currently online and stable?

No sign of RustTime | Moscow X2 02.10 at present: it was last seen 28 hours ago. The uptime figure it gives suggests it restarted around 23 hours ago. It was up 63% of the time across the last 7 full days: 106 of 168 hours. Rust Zerg Life has been tracking it since 13 September 2026.

How well does RustTime | Moscow X2 02.10 perform?

Server fps held an average of 141 for the last 48 hours, with a minimum of 99. The world held as many as 70,179 entities, including buildings, deployables and everything else. At its highest, memory usage hit 2,551 MB. Lag, as players feel it, is caused by low fps and an increasing number of entities.

What version is RustTime | Moscow X2 02.10 using?

Rust network protocol 2634 and build 167398 is what RustTime | Moscow X2 02.10 runs, on Linux. You can only join if your game uses the same protocol, and Steam takes care of updating it.

What is the location of RustTime | Moscow X2 02.10?

From RustTime | Moscow X2 02.10, no region is published. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 5.35.96.35:31008.

Wipe cycle

What can you expect on wipe day on RustTime | Moscow X2 02.10?

The average peak for its recent wipes was 12 players. The crowd on the latest wipe peaked 0 hours in. The crowd kept above half that peak until the next wipe in 50% of its recent wipes. Otherwise, it slipped below half by day 3.

What schedule does RustTime | Moscow X2 02.10 follow for wipes?

There is no next wipe to predict: RustTime | Moscow X2 02.10 wipes at irregular times. Come Thursday 5 November at 19:00 UTC, the monthly force wipe arrives for every Rust server. The world in play right now was made 3 days 22 hours ago.

How to join

How can I connect to RustTime | Moscow X2 02.10?

You can join by opening the console with F1 and typing client.connect 5.35.96.35:31008. Or hit Launch Rust on this page to open Rust through Steam and connect. 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 in the standard Rust mode.
mp244
Max players Capacity: 244.
ts8
Group limit Teams max out at 8—the default setting for Rust.
v2634
Protocol You'll need protocol 2634 on your game to join.
cs167398
Build The game build is 167398.
ptrak
Networking The network layer is RakNet, which is standard.
$r?
Region code There's no region code here.

Mods and access

^z
Modded The Modded listing means plugins or settings have changed the game.
^y
Carbon Carbon plugin framework is running.

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.