Rust Server TrendsSeismic network · station log
Recording Stations11,618 Players41,424 Active3,040 Wipes · 3 h89 48 h

Station XX-12581 · recording

RustTime | Moscow X2 02.10

Online 5.35.96.35:31008 checked 9m ago

2x moddedcarbon
Connect
Players now
0/ 244
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#12,581
top 57%
Last wipe
17d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-12581 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 244 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+0into Wed 06:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75108:0017:0002:0012:0021:0006:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040008:0017:0002:0012:0021:0006: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.

Channel 3 · rank movement

Rank

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

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

Expected events

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 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
12players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 10 Oct, 11:01 UTC17d ago M0.6rising 5 – running 1
Fri 2 Oct, 14:19 UTC25d ago M1.2rising 15 halved by day 3 7.9 days 0
Fri 2 Oct, 05:09 UTC26d ago M1.2rising 15 – 0.4 days 0
Fri 25 Sep, 14:23 UTC32d ago M1.0rising 9 held half 6.6 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 730 on average
458/ 500
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 546 on average
291/ 300
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 353 on average
119/ 150
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 325 on average
96/ 150
Magic Rust #18 — Vanilla 2x | Pyccкий EU · groups of 150+ · 2x · weekly · 323 on average
27/ 100
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 299 on average
151/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on RustTime | Moscow X2 02.10?

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

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

2x gather is what RustTime | Moscow X2 02.10 runs, judging by its name. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on RustTime | Moscow X2 02.10?

At this moment, RustTime | Moscow X2 02.10 records 0 players across 244 slots. Across seven days this server recorded an average of 0 players and a peak of 1. The busiest point in the last 48 hours came at 05:00 UTC, averaging 0 players.

How does RustTime | Moscow X2 02.10 rank against other Rust servers?

Over the last seven days, RustTime | Moscow X2 02.10 recorded enough player hours to reach #12,581 worldwide, placing it in the top 57% of all ranked servers.

Server details

How reliably does RustTime | Moscow X2 02.10 stay online?

RustTime | Moscow X2 02.10 is up at the moment. Going by the uptime figure it reports, it restarted about 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does RustTime | Moscow X2 02.10 perform under load?

Its average server fps over the last 48 hours was 162, and it never dropped below 98. The world held up to 69,913 entities at its peak, buildings and deployables included. Memory use peaked at 2,738 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does RustTime | Moscow X2 02.10 run from?

No region is published by RustTime | Moscow X2 02.10. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 5.35.96.35:31008.

Which Rust version is RustTime | Moscow X2 02.10 running?

RustTime | Moscow X2 02.10 is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on RustTime | Moscow X2 02.10?

The recent wipes averaged a busiest count of 12 players. The peak on the most recent wipe came 0 hours after the wipe. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. It fell under half by day 3 in the wipes where it didn't hold.

How often does RustTime | Moscow X2 02.10 wipe, and on which days?

No next wipe can be predicted for RustTime | Moscow X2 02.10, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 17 days 20 hours.

Lists and tags

What do the server tags on RustTime | Moscow X2 02.10 mean?

These are the tags RustTime | Moscow X2 02.10 publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp244 (Max players): Slots: 244; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does RustTime | Moscow X2 02.10 appear?

You will find RustTime | Moscow X2 02.10 on the following Rust Server Trends lists: 2x Rust servers, listed live and Modded Rust servers, tracked live. 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.

How to join

What steps get you onto RustTime | Moscow X2 02.10?

To join, enter client.connect 5.35.96.35:31008 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://rusttimes.gamestores.app/.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp244
Max players Slots: 244.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.