Rust Data LabData lab · live
Live readings Servers11,811 Players72,496 Populated3,745 Fresh wipes · 3h137 Sampled every 5 min

Element card · group Modded · atomic number 3,115, its rank

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

Online 46.174.55.78:28015 checked 13m ago

2x trio biweekly wipes moddedoxide
Join the experiment
Atomic mass · players now 1/ 250 0% full Room to join
7-day average1peak 6
Rank · atomic number#3,115top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 21hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
05010015020022:0007:0016:0002:0011:0020: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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct19 Oct23 Oct27 Oct

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

Reaction kinetics

Wipe schedule

from its schedule tag

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

  1. 8d 21hThu 5 Nov, 19:00 UTCFW
  2. 9d 19hFri 6 Nov, 16:54 UTC
  3. 23d 19hFri 20 Nov, 16:54 UTC
  4. 36d 21hThu 3 Dec, 19:00 UTCFW
  5. 37d 19hFri 4 Dec, 16:54 UTC

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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 16:54 UTC4d ago 6 – running 0
Fri 16 Oct, 15:22 UTC11d ago 3 held half 7.1 days 1
Thu 15 Oct, 09:09 UTC12d ago 3 – 1.3 days 0
Thu 8 Oct, 23:23 UTC18d 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
  1. 1 Su SURVIVORS.GG #… 38
    SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] FULLWIPED 25.10 trio · 2x · biweekly · 137 on average 38/ 200
  2. 2 Ho HollowServers.… 12
    HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED NA · trio · 2x · biweekly · 10 on average 12/ 150
  3. 3 Ho HollowServers.… 3
    HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPED EU · trio · 2x · biweekly · 3 on average 3/ 150
  4. 4 Пр ПРОСТОЙ #1 MAX… 0
    ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ] EU · trio · 2x · biweekly · 2 on average 0/ 150
  5. 5 Pr » ProjectGamin… 4
    » ProjectGaming.gg | 2X Vanilla | Solo/Duo/Trio | WIPED 10/25 trio · 2x · biweekly · 1 on average 4/ 150
  6. 6 Ru #3 [RU] ДЛЯ НО… 0
    #3 [RU] ДЛЯ НОВИЧКОВ X2|MAX3|ORP|SHOP|R7ZONE.RU EU · trio · 2x · biweekly · 1 on average 0/ 300

Quick answers

from the figures on this page

Server setup

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

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs a procedural map of size 4,500 with seed 1337; the game generates it. The map repeats when size and seed match, and you can view it on RustMaps from this page. The name of the map is: Custom Map.

How is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS configured, and what rules apply?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS carries a 2x gather rate, as its name states. The group cap is 3 players (trio). survival is the game mode, raiding, building and gathering: the standard game. You can fight other players and raid them. In the server browser it sits under Modded: the game is changed by plugins or settings. Oxide plugins are running on it. Anti-cheat is on: Valve's VAC.

Server facts

What region hosts KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Nothing about a region is published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Rust Data Lab shows a server's stated location, not a verified position of the machine. 46.174.55.78:28015 is the address it uses.

On what Rust version does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS operate?

On Linux, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is running Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam takes care of updating it.

Does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS stay up, and how reliable is its uptime?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is live as of now. According to the uptime it reports, the last restart was about 5 hours ago. For the last 7 full days, 168 of 168 hours were online, giving 100% uptime. It first appeared to Rust Data Lab on 8 October 2026.

How well does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS perform?

In the last 48 hours, it averaged 81 server fps, with a low of 60. The maximum entity count was 144,029, covering buildings, deployables and all else in the world. Memory use peaked at 6,373 MB. Players feel lag when fps is low and the entity count climbs.

Wipe schedule

When does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS wipe, and how often?

Its tag guides the prediction, since KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's record holds too few wipes to confirm a schedule. The next time this server wipes will be the force wipe on Thursday 5 November at 19:00 UTC, which wipes every Rust server. The world it is running now dates from 4 days 4 hours ago. Wipes every two weeks are what its tags set out.

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

Averaged across its recent wipes, the busiest point drew 4 players. 40 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

Where it appears

What should you understand from the tags KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS carries?

gmrust (Game mode): Standard Rust survival is the game here; mp250 (Max players): Player slots: 250; ts3 (Group limit): No team may exceed 3; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank; ^b (Biweekly): Every two weeks, the server wipes; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Because plugins or settings change the game, it is filed under Modded; jp0 (Custom tag): A plugin or the owner set this tag; it is not standard Rust; oxidation (Custom tag): A plugin or the owner set this tag; it is not standard Rust: that is the tag list KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS publishes, and the game's server browser reads it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Which Rust Data Lab filters and lists does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS appear in?

These themed Rust Data Lab lists carry KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: 2x gather rate servers, Modded Rust servers, measured, Aim training servers, measured live and Trio Rust servers, measured live. Applying these filters on the server list returns it: 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 counts

How does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS compare with other servers in the rankings?

Player hours over the last week put KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,115, inside the top 14% of ranked servers. In the trio category it ranks #233.

What does the current player count on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS tell you?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS currently shows 1 players across 250 slots. Averaged over the past week: 1 players, peaking at 6. The busiest point in the last 48 hours came at 16:00 UTC, averaging 3 players.

Connection

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

Open the console with F1 in Rust and type client.connect 46.174.55.78:28015. The Launch Rust button on this page does the same job through Steam. You can find its website at https://kaiman12rus.ru.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp250
Max players Player slots: 250.
ts3
Group limit No team may exceed 3.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

Wipe schedule

^b
Biweekly Every two weeks, the server wipes.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Because plugins or settings change the game, it is filed under Modded.

Other

jp0
Custom tag A plugin or the owner set this tag; it is not standard Rust.
oxidation
Custom tag A plugin or the owner set this tag; it is not standard Rust.

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.