Rust Data

rustdata.spaceservers46.174.55.78:28016.ipynb

Run all rust-data · live

‹ All servers

Online 46.174.55.78:28015 checked 2h ago

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

2x trio biweekly wipes moddedoxide

Connect

srv = rust.server("46.174.55.78:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 3/250 # 1% full
7-day average 1 # peak 6
rank #3,188 # top 14%
last wipe 5d ago # biweekly schedule
next wipe 7d 23h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020020: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 8 Oct. 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
15k10k15k20k8 Oct12 Oct16 Oct20 Oct24 Oct28 Oct

Top 14% of all ranked servers, and #237 of the trio servers (top 38%). Ranked on player hours over the last seven days.

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h. # The force wipe · high confidence

usual gap6.4 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak4players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

inatkind
07d 23hThu 5 Nov, 19:00 UTCFW force wipe
18d 21hFri 6 Nov, 16:54 UTCwipe
222d 21hFri 20 Nov, 16:54 UTCwipe
335d 23hThu 3 Dec, 19:00 UTCFW force wipe
436d 21hFri 4 Dec, 16:54 UTCwipe

The first 48 hours of its last wipes

Fri 23 OctFri 16 OctThu 15 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 40 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 16:54 UTC5d ago 6 NaN running 0
1 Fri 16 Oct, 15:22 UTC12d ago 3 held half 7.1 days 1
2 Thu 15 Oct, 09:09 UTC13d ago 3 NaN 1.3 days 0
3 Thu 8 Oct, 23:23 UTC19d ago 3 held half 6.4 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.

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

Map

4500 · seed 1337
Map of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS
map
Custom Map
size
4500
seed
1337

Server

srv.info()
address
46.174.55.78:28015
region
–
max players
250
group limit
trio
wipe schedule
biweekly
last wipe
23 Oct 2026, 16:54 UTC
hostname
–
first seen
8 Oct 2026

About this server · in its own words

print(srv.description)
KAIMAN RUST X2 • MAX3 • PvP Квесты • Ивенты • NPC • Raidable Bases Киты • Телепорты • Экономика • Статистика Честный баланс и активная администрация

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

rust.similar(srv).head(6)
serverlike_thisplayers
0SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] WIPED 28.10trio · 2x · biweekly · 130 on average739/750
1HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 10 on average6/150
2HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPEDEU · trio · 2x · biweekly · 3 on average3/150
3ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ]EU · trio · 2x · biweekly · 2 on average2/150
4» ProjectGaming.gg | 2X Vanilla | Solo/Duo/Trio | WIPED 10/25trio · 2x · biweekly · 2 on average5/150
5#3 [RU] ДЛЯ НОВИЧКОВ X2|MAX3|ORP|SHOP|R7ZONE.RUEU · trio · 2x · biweekly · 1 on average2/300

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS rank?

Player hours over seven days put KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,188, in the top 14% of the ranked set. Its position in the trio group is #237.

What population does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS carry?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS reports 3 players at this refresh, with 250 slots configured. Over the last seven days it averaged 1 players and peaked at 6. Peak hour in the last 48 hours: 17:00 UTC, mean 3 players.

Server facts

How smoothly does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS run?

Server fps over the last 48 hours averages 84; the floor is 68. Buildings, deployables and all else in the world took the count as high as 144,360 entities. The memory field tops out at 6,373 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Steam updates your game for you, but the protocol must match to join.

How reliable is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, and is it online now?

The current sample puts KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS online. The uptime it reports puts the last restart about 1 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 8 October 2026.

Which location does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS run from?

No region is published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 46.174.55.78:28015.

Settings and map

Which settings and rules does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS run?

The name carries the figure: KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs 2x gather. Up to 3 players may share a group (trio). survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.

What is the map on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs a procedural map of size 4,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.

Wipe data

When does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS wipe, and on what schedule?

The prediction follows the tag, because KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's wipes on record are too few to confirm the schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 5 days 2 hours ago. Its tags carry a wipe schedule of every two weeks.

What is wipe day on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS like?

Across recent wipes the busiest point averaged 4 players. The crowd on the latest wipe topped out 40 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags and filters

Which Rust Data filters and lists contain KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

The Rust Data lists that KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS fits are: Modded Rust servers, 2x Rust servers, Rust aim training servers and Trio Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Every two weeks; Last wipe: In the last week; Gather rate: 2x.

How should you read the server tags on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Read by the game's server browser, the tags KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS publishes are: gmrust (Game mode): Rust survival in its standard form; mp250 (Max players): The server lists 250 slots; ts3 (Group limit): Team size tops out at 3; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game; jp0 (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin; oxidation (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way to join KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

In Rust, F1 opens the console: type client.connect 46.174.55.78:28015. Launch Rust on this page does the same by opening the game through Steam and connecting. https://kaiman12rus.ru is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp250,ptrak,jp0,$r?,v2635,^b,gmrust,cs168909,ts3,^o^z,oxidation

Game

gmrust
Game mode Rust survival in its standard form.
mp250
Max players The server lists 250 slots.
ts3
Group limit Team size tops out at 3.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

Other

jp0
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.
oxidation
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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 89,289 players 11,829 servers online