StatusLive Servers online11,829 Players89,289 Populated4,008 Wiped · 3 h50 Interval5 min Date28 OCT 2026

DWG RG-S12493Server sheetchecked 2h ago

RustTime | Moscow X2 02.10

Online 5.35.96.35:31008 checked 2h ago

2x moddedcarbon
Connect
Players now 0/ 244 0% full
7-day average0peak 1
Rank#12,493top 56%
Last wipe18d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.250.50.75120:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Fig. 1Players on RustTime | Moscow X2 02.10
Fig. 2

Server performance

010020030040020:0005:0014:0023:0008:0017: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak12players, 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 11:01 UTC18d ago 5 – running 1
Fri 2 Oct, 14:19 UTC26d 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 UTC33d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 778 on average
938 / 1000
02
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 582 on average
678 / 700
03
Atlas - US 2X Monthly | Vanilla+ | No BP WipesNA · groups of 16+ · 2x · monthly · 362 on average
168 / 200
04
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 341 on average
365 / 385
05
Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 321 on average
1481 / 1550
06
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 309 on average
348 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is RustTime | Moscow X2 02.10 online, and what uptime has been recorded?

At this moment RustTime | Moscow X2 02.10 is online. About 11 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. First seen by Rust Graphs on 13 September 2026.

What does the recorded performance of RustTime | Moscow X2 02.10 show?

Average server fps over the last 48 hours is 163; the lowest was 98. Counted at its highest: 69,738 entities, buildings, deployables and the rest of the world included. Memory use peaked at 2,738 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for RustTime | Moscow X2 02.10?

There is no region published by RustTime | Moscow X2 02.10. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 5.35.96.35:31008.

On which Rust version is RustTime | Moscow X2 02.10 running?

Rust network protocol 2635 and build 168909 on Linux: that is what RustTime | Moscow X2 02.10 runs. To join, your game must be on the same protocol; Steam handles the update.

Player data

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

0 of 244 slots on RustTime | Moscow X2 02.10 are taken at the latest refresh. The seven-day mean is 0 players; the peak over the same period is 1. The 48-hour peak falls at 05:00 UTC, averaging 0 players.

Against other Rust servers, where is RustTime | Moscow X2 02.10 placed?

Over the last seven days, RustTime | Moscow X2 02.10 records #12,493 for player hours: the top 56% of all ranked servers.

Schedules

What happens on RustTime | Moscow X2 02.10 on the day of a wipe?

The recent wipes averaged a busiest count of 12 players. At 0 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 50% of its recent wipes. By day 3 the crowd had fallen below half on the wipes where it did not hold.

Which times and days are wipes plotted at on RustTime | Moscow X2 02.10?

There is no next wipe to predict at RustTime | Moscow X2 02.10, which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 18 days 8 hours ago.

Settings

What settings and rules apply on RustTime | Moscow X2 02.10?

The name records 2x gather for RustTime | Moscow X2 02.10. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. The server browser lists it under Modded: plugins or settings change the game. Carbon plugins are run on it. VAC is on: that is Valve's anti-cheat.

What is the map for 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. Size and seed fix the map, so this page links it on RustMaps for viewing.

Tags

On Rust Graphs, which lists and filters contain RustTime | Moscow X2 02.10?

On Rust Graphs, RustTime | Moscow X2 02.10 is placed in these lists: Servers with a 2x gather rate and Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.

On RustTime | Moscow X2 02.10, what is meant by each tag?

gmrust (Game mode): Standard survival, as Rust plays; mp244 (Max players): 244 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Carbon is the plugin framework here are the tags RustTime | Moscow X2 02.10 publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

How to join

By what method do you join RustTime | Moscow X2 02.10?

Enter client.connect 5.35.96.35:31008 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://rusttimes.gamestores.app/ is its website.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp244,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Standard survival, as Rust plays.
mp244
Max players 244 player slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol Your game must match protocol 2635 to join.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The region code field is empty.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon Carbon is the plugin framework here.

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.

KeyTag string decoded