Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO K SRV11,604online PAX34,824playing OCC2,902with players WIPED 3H67
MODModded traffic
Callsign

RST13147=

RustTime | Moscow X2 02.10

Online 5.35.96.35:31008 checked 10m ago

2x moddedcarbon
Clearance · join
Players now 0/ 244 0% full
7-day average0peak 1
Rank#13,147top 59%
Last wipe17d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeak
00.250.50.75107:0016:0001:0010:0019:0004:00

Hourly average and peak, UTC.

Server performance

010020030040007:0016:0001:0010:0019:0004: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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Flight plan

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

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 UTC17d ago 5 – running 1
Fri 2 Oct, 14:19 UTC25d 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 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign ATL015EU · groups of 16+ · 2x · monthly · 728 on average Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes
    Players 366/350
  2. 02MOD
    Callsign VTL015EU · groups of 16+ · 2x · monthly · 544 on average Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes
    Players 230/225
  3. 03MOD
    Callsign ATL015NA · groups of 16+ · 2x · monthly · 352 on average Atlas - US 2X Monthly | Vanilla+ | No BP Wipes
    Players 124/150
  4. 04MOD
    Callsign RNG017EU · groups of 50+ · 2x · monthly · 325 on average EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr
    Players 60/150
  5. 05MOD
    Callsign MGC010EU · groups of 150+ · 2x · weekly · 323 on average Magic Rust #18 — Vanilla 2x | Pyccкий
    Players 15/100
  6. 06MOD
    Callsign MRG002EU · groups of 300+ · 2x · weekly · 299 on average MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10
    Players 98/1000
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which lists and filters on Rust Tracker show RustTime | Moscow X2 02.10?

On Rust Tracker, RustTime | Moscow X2 02.10 sits in these lists: 2x Rust servers, tracked live and Modded servers, tracked live. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.

What do the tags mean that RustTime | Moscow X2 02.10 is listed under?

The game's server browser reads these tags from RustTime | Moscow X2 02.10: gmrust (Game mode): Survival as standard Rust plays; mp244 (Max players): Slots: 244; ts8 (Group limit): Team limit is 8, the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset; ^z (Modded): The game is changed by plugins or settings; listed under Modded; ^y (Carbon): Carbon is installed — a plugin framework. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

What should you expect on RustTime | Moscow X2 02.10 when wipe day lands?

Recent wipes averaged a peak of 12 players. 0 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. By day 3 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for RustTime | Moscow X2 02.10?

No next wipe to predict for RustTime | Moscow X2 02.10, which wipes at irregular times. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. Its world went live 17 days 19 hours.

Server Details

Is RustTime | Moscow X2 02.10 up, and how does its uptime hold?

RustTime | Moscow X2 02.10 is up and online at this moment. By its own uptime figure, the last restart was roughly 23 hours ago. Uptime stood at 100% for the last 7 full days, 168 of 168 hours online. The first sighting by Rust Tracker was 13 September 2026.

What Rust version is RustTime | Moscow X2 02.10 on?

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

Is RustTime | Moscow X2 02.10 holding performance?

For the last 48 hours it averaged 162 server fps; the floor was 98. Buildings, deployables and the rest of the world took it to a maximum of 69,913 entities. Peak memory use: 2,738 MB. A climbing entity count and low fps are what register as lag for players.

Where does RustTime | Moscow X2 02.10 sit?

Nothing on region from RustTime | Moscow X2 02.10; none is published. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 5.35.96.35:31008.

Population

How many players are on RustTime | Moscow X2 02.10 right now?

Slots 244; players on board 0: that is RustTime | Moscow X2 02.10 now. Over seven days: average 0, peak 1 players. Busiest window in 48 hours: 04:00 UTC, 0 players on average.

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

Top 59% of all ranked servers, and #13,147 on seven-day player hours: RustTime | Moscow X2 02.10.

Settings

Which settings and rules are confirmed on RustTime | Moscow X2 02.10?

2x gather is what RustTime | Moscow X2 02.10 runs, going by its name. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build, raid, as the game intends. Fighting and raiding between players are on. The server browser lists it under Modded, where plugins or settings change the game. The plugin count stands at Carbon. VAC is on, Valve's anti-cheat.

Which map is loaded on RustTime | Moscow X2 02.10?

Generated by the game from seed 347556993, the procedural map on RustTime | Moscow X2 02.10 measures 3,500. Same size, same seed, same map. RustMaps shows it, linked from this page.

How to Join

What is the way to join RustTime | Moscow X2 02.10?

Open the console in Rust with F1 after starting the game, then type client.connect 5.35.96.35:31008. Alternatively, Launch Rust here opens Rust via Steam and connects you. The server's website: https://rusttimes.gamestores.app/.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp244
Max players Slots: 244.
ts8
Group limit Team limit is 8, the game default.
v2635
Protocol Your game must be on protocol 2635 to connect.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer — the game's standard.
$r?
Region code The region code is unset.

Mods and access

^z
Modded The game is changed by plugins or settings; listed under Modded.
^y
Carbon Carbon is installed — a plugin framework.

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.