Rust Server TrendsSeismic network · station log
Recording Stations11,897 Players102,621 Active3,980 Wipes · 3 h399 48 h

Station XX-15869 · no signal

KAZANRUST X2 [MAX 3] DLC WIPE 2.10

Offline 194.147.90.25:35007 checked 18d ago

2x trio moddedoxide
Connect
Players now
0/ 400
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,869
top 72%
Last wipe
25d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15869 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 400 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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 27 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
15k10k15k20k27 Sep1 Oct5 Oct9 Oct13 Oct17 Oct

Top 72% of all ranked servers, and #508 of the trio servers (top 84%). Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap
3 daysbetween real wipes
wipe-day peak
2players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctTue 29 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 38 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 05:15 UTC27d ago M0.0rising 1 – running 0
Tue 29 Sep, 06:10 UTC30d ago M0.0rising 3 held half 3 days 2

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
MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 24.10 EU · trio · 2x · weekly · 257 on average
25/ 500
WARBANDITS.GG EU 2X |Solo/Duo/Trio|X2 JUST FULLWIPED EU · trio · 2x · weekly · 225 on average
839/ 850
WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPED NA · trio · 2x · weekly · 189 on average
24/ 200
Magic Rust #7 — Modded 2x (Solo/Duo/Trio) | Pyccкий EU · trio · 2x · weekly · 178 on average
92/ 130
Magic Rust #24 — Vanilla 2x (Solo/Duo/Trio) | Pyccкий EU · trio · 2x · weekly · 142 on average
255/ 320
MIRAGE RUST | MONDAY SOLO/DUO/TRIO 2x | Wipe 26.10 EU · trio · 2x · weekly · 137 on average
112/ 350
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

The procedural map on KAZANRUST X2 [MAX 3] DLC WIPE 2.10 is size 3,500 with seed 1971592713, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

2x gather is what KAZANRUST X2 [MAX 3] DLC WIPE 2.10 runs, judging by its name. 3 players is the most a group can hold (trio). survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. Anti-cheat is on: VAC, from Valve.

Live population

What is the current population on KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

KAZANRUST X2 [MAX 3] DLC WIPE 2.10 is not responding at this moment and is offline, last seen 18 days 23 hours ago.

How does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 rank against other Rust servers?

The last seven days of player hours place KAZANRUST X2 [MAX 3] DLC WIPE 2.10 at #15,869, in the top 72% of all ranked servers. The ranking for trio puts it at #508.

Server facts

How reliably does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 stay online?

As recorded now, KAZANRUST X2 [MAX 3] DLC WIPE 2.10 is not reachable, the last contact having been 18 days 23 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 27 September 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is KAZANRUST X2 [MAX 3] DLC WIPE 2.10 hosted?

No region is published by KAZANRUST X2 [MAX 3] DLC WIPE 2.10. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 194.147.90.25:35007.

What build of Rust does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 use?

KAZANRUST X2 [MAX 3] DLC WIPE 2.10 is running Rust network protocol 2634 and build 166652 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

2 players, on average, was the busiest crowd at its recent wipes. 38 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.

How often does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 wipe, and on which days?

On record so far are too few of KAZANRUST X2 [MAX 3] DLC WIPE 2.10's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 25 days 23 hours is how long the current world has been running.

Tags

What do the server tags on KAZANRUST X2 [MAX 3] DLC WIPE 2.10 mean?

Tags published by KAZANRUST X2 [MAX 3] DLC WIPE 2.10 and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp400 (Max players): The server has 400 slots; ts3 (Group limit): Teams are capped at 3 players; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): It runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. 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 KAZANRUST X2 [MAX 3] DLC WIPE 2.10 appear?

These Rust Server Trends lists include KAZANRUST X2 [MAX 3] DLC WIPE 2.10: 2x Rust servers, listed live, Modded Rust servers, tracked live and Best trio Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Gather rate: 2x.

Connecting

How do you connect to KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

You can connect by pressing F1 in Rust and typing client.connect 194.147.90.25:35007 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp400,ptrak,$r?,v2634,gmrust,cs166652,ts3,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp400
Max players The server has 400 slots.
ts3
Group limit Teams are capped at 3 players.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs166652
Build It runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.