Rust Data

rustdata.spaceservers194.147.90.25:36000.ipynb

Run all rust-data · live

‹ All servers

Offline 194.147.90.25:35007 checked 18d ago

KAZANRUST X2 [MAX 3] DLC WIPE 2.10

2x trio moddedoxide

Connect

srv = rust.server("194.147.90.25:36000")
print(srv.connect_command)

Right now

srv.summary()
players now 0/400 # 0% full
7-day average 0 # peak –
rank #15,869 # top 72%
last wipe 25d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 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.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap3 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held100%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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 05:15 UTC27d ago 1 NaN running 0
1 Tue 29 Sep, 06:10 UTC30d ago 3 held half 3 days 2

# 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.

display(srv.map, srv.info())

Map

3500 · seed 1971592713
Map of KAZANRUST X2 [MAX 3] DLC WIPE 2.10
map
Procedural Map
size
3500
seed
1971592713
Open on RustMaps

Server

srv.info()
address
194.147.90.25:35007
region
–
max players
400
group limit
trio
wipe schedule
–
last wipe
3 Oct 2026, 18:48 UTC
hostname
–
first seen
27 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 24.10EU · trio · 2x · weekly · 256 on average26/500
1WARBANDITS.GG EU 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDEU · trio · 2x · weekly · 233 on average30/200
2WARBANDITS.GG 2X |Solo/Duo/Trio|X2 JUST FULLWIPEDNA · trio · 2x · weekly · 189 on average9/200
3Magic Rust #7 — Modded 2x (Solo/Duo/Trio) | PyccкийEU · trio · 2x · weekly · 176 on average92/120
4Magic Rust #24 — Vanilla 2x (Solo/Duo/Trio) | Baйп 26.10EU · trio · 2x · weekly · 135 on average199/300
5SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] WIPED 28.10trio · 2x · biweekly · 134 on average163/200

Quick answers

From the figures on this page.

Population

How does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 compare in the rankings?

Player hours over seven days put KAZANRUST X2 [MAX 3] DLC WIPE 2.10 at #15,869, in the top 72% of the ranked set. Its position in the trio group is #508.

What population does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 carry?

Offline now for KAZANRUST X2 [MAX 3] DLC WIPE 2.10, with the last sample 18 days 16 hours ago.

Server facts

Which Rust version is KAZANRUST X2 [MAX 3] DLC WIPE 2.10 on?

Rust network protocol 2634 and build 166652 on Windows is what KAZANRUST X2 [MAX 3] DLC WIPE 2.10 runs. The protocol has to match before you can join, and Steam does the updating.

Is KAZANRUST X2 [MAX 3] DLC WIPE 2.10 up, and what does its uptime show?

The latest sample has KAZANRUST X2 [MAX 3] DLC WIPE 2.10 offline, with a last sighting 18 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 27 September 2026.

Where does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 sit?

No region is published by KAZANRUST X2 [MAX 3] DLC WIPE 2.10. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 194.147.90.25:35007.

Rules, settings, map

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

Gather sits at 2x, read from the server's own name: KAZANRUST X2 [MAX 3] DLC WIPE 2.10. trio sets the cap: 3 players per group. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.

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

Size 3,500, seed 1971592713: the procedural map on KAZANRUST X2 [MAX 3] DLC WIPE 2.10, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe data

On what schedule does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 wipe?

Too few wipes are on record for KAZANRUST X2 [MAX 3] DLC WIPE 2.10 to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 25 days 15 hours ago.

On KAZANRUST X2 [MAX 3] DLC WIPE 2.10, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 38 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.

Lists and tags

Where does KAZANRUST X2 [MAX 3] DLC WIPE 2.10 appear among Rust Data lists and filters?

On Rust Data, KAZANRUST X2 [MAX 3] DLC WIPE 2.10 appears in these lists: Modded Rust servers, 2x Rust servers and Trio Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Gather rate: 2x.

How should you read the server tags on KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

Read by the game's server browser, the tags KAZANRUST X2 [MAX 3] DLC WIPE 2.10 publishes are: gmrust (Game mode): Rust survival in its standard form; mp400 (Max players): 400 slots in total; ts3 (Group limit): No team may exceed 3; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

How can I connect to KAZANRUST X2 [MAX 3] DLC WIPE 2.10?

In Rust, F1 opens the console: type client.connect 194.147.90.25:35007. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp400
Max players 400 slots in total.
ts3
Group limit No team may exceed 3.
v2634
Protocol To join, your game must run protocol 2634.
cs166652
Build Build number: 166652.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits 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.

Rust Data 55,754 players 11,716 servers online