Rust Server Analytics 40,937 players11,633 servers
All servers
Drill-through Server detail

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

Online 46.174.55.78:28015 checked 9m ago

Drill-through
FilterServeris KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS
Attributes
2x trio biweekly wipes moddedoxide
Last refreshed
Players now 0/ 250
7-day average 1 peak 6
Rank #3,233 top 15%
Last wipe 6d ago biweekly schedule
Next wipe 6d 14h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123405:0014:0000:0009:0018:0003:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020005:0014:0000:0009:0018:0003: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
RankRank in region
15k10k15k20k8 Oct12 Oct17 Oct21 Oct26 Oct30 Oct

Top 15% of all ranked servers, and #240 of the trio servers (top 39%). Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 6d 14h. 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

InWhen, UTCKind
6d 14hThu 5 Nov, 19:00 UTCFW force wipe
7d 12hFri 6 Nov, 16:54 UTCits own
21d 12hFri 20 Nov, 16:54 UTCits own
34d 14hThu 3 Dec, 19:00 UTCFW force wipe
35d 12hFri 4 Dec, 16:54 UTCits own

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
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 16:54 UTC6d ago 6 – running 0
Fri 16 Oct, 15:22 UTC13d ago 3 held half 7.1 days 1
Thu 15 Oct, 09:09 UTC14d ago 3 – 1.3 days 0
Thu 8 Oct, 23:23 UTC21d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] WIPED 28.10 trio · 2x · biweekly · 134 on average 18 / 200
HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED NA · trio · 2x · biweekly · 12 on average 27 / 150
HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPED EU · trio · 2x · biweekly · 3 on average 2 / 150
ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ] EU · trio · 2x · biweekly · 2 on average 0 / 150
» ProjectGaming.gg | 2X Vanilla | Solo/Duo/Trio | WIPED 10/25 trio · 2x · biweekly · 2 on average 0 / 150
MIRAGE RUST | SATURDAY SOLO/DUO/TRIO 2x | Wipe 24.10 EU · trio · 2x · weekly · 239 on average 1 / 500

Quick answers

from the figures on this page

Wipe cycle

The wipe schedule for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: what is it?

The prediction follows its tag, because too few of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's wipes are on record to confirm the schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world now in play was created 6 days 11 hours ago. Its tags publish a wipe schedule of every two weeks.

On KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, what happens on wipe day?

Across recent wipes the busiest point averaged 4 players. 40 hours after the latest wipe the crowd peaked. Above half that peak until the next wipe held in 100% of recent wipes.

Server

In which region does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS sit?

No region is published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 46.174.55.78:28015.

What Rust build does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS run?

On Linux, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.

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

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS reports online at the current check. The uptime it reports puts the last restart at about 4 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. 8 October 2026 is when Rust Server Analytics first recorded it.

Is performance on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS stable?

Over 48 hours the average held at 81 server fps, and the minimum was 59. Buildings, deployables and all other world objects brought the entity total to 146,291. Peak memory was 6,371 MB. A climbing entity count and low fps are the lag players perceive.

Lists and tags

What do KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's tags stand for?

Tags from KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, as read by the game's server browser, are: gmrust (Game mode): Rust survival, standard ruleset; mp250 (Max players): Capacity of 250 slots; ts3 (Group limit): Teams hold no more than 3; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^b (Biweekly): Every two weeks the server wipes; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Modded listing, where plugins or settings change the game; jp0 (Custom tag): Outside the standard tag set, added by the owner or a plugin; oxidation (Custom tag): Outside the standard tag set, added by the owner or a plugin. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

These Rust Server Analytics lists include KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: Rust servers with a 2x gather rate, Modded Rust servers: live data, Rust aim training servers and Trio Rust servers, live. On the server list, the filters that return it are: 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.

Player numbers

Where does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS sit among Rust servers?

On player hours over seven days, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS ranks #3,233, within the top 15% of ranked servers. In the trio peer group, the rank is #240.

What is the population of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Of 250 slots, 0 are filled on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at this refresh. Averaging 1 players across seven days, the server reached a peak of 6. The 48-hour peak window is 17:00 UTC, at an average of 3 players.

Map and rules

What settings and rules does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS use?

2x gathering is what KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS states in its name. Groups: trio, capped at 3 players. survival is the game mode, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. The server runs with VAC, Valve's anti-cheat, enabled.

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

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS uses a procedural map of size 4,500 with seed 1337, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here. The map is called Custom Map.

How to join

How do you connect to KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

In the Rust console (F1), enter client.connect 46.174.55.78:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://kaiman12rus.ru is its website.

Server tags

what each one means

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

Game

gmrust
Game mode Rust survival, standard ruleset.
mp250
Max players Capacity of 250 slots.
ts3
Group limit Teams hold no more than 3.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Wipe schedule

^b
Biweekly Every two weeks the server wipes.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded Modded listing, where plugins or settings change the game.

Other

jp0
Custom tag Outside the standard tag set, added by the owner or a plugin.
oxidation
Custom tag Outside the standard tag set, added 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.