StatusLive Servers online11,800 Players69,961 Populated3,675 Wiped · 3 h123 Interval5 min Date28 OCT 2026

DWG RG-S3200Server sheetchecked 12m ago

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

Online 46.174.55.78:28015 checked 12m ago

2x trio biweekly wipes moddedoxide
Connect
Players now 2/ 250 1% full
7-day average1peak 6
Rank#3,200top 14%
Last wipe5d agobiweekly schedule
Next wipe7d 21hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
0123422:0007:0016:0001:0010:0020:00

Hourly average and peak, UTC.

Fig. 1Players on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS
Fig. 2

Server performance

05010015020022:0007:0016:0001:0010: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 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. 7d 21hThu 5 Nov, 19:00 UTCFW
  2. 8d 19hFri 6 Nov, 16:54 UTC
  3. 22d 19hFri 20 Nov, 16:54 UTC
  4. 35d 21hThu 3 Dec, 19:00 UTCFW
  5. 36d 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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

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

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] WIPED 28.10trio · 2x · biweekly · 129 on average
514 / 575
02
HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 10 on average
6 / 150
03
HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPEDEU · trio · 2x · biweekly · 3 on average
2 / 150
04
[EU] HUNTED 2x | Trio | Bounty | Raid Bases | BossEU · trio · 2x · biweekly · 2 on average
0 / 75
05
ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ]EU · trio · 2x · biweekly · 2 on average
1 / 150
06 4 / 150
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, and is it up?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is up at this moment. The uptime it reports puts the last restart at about 5 hours ago. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. The first sighting of it by Rust Graphs was on 8 October 2026.

What does the recorded performance of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS show?

The last 48 hours give an average of 84 server fps and a floor of 68. Counted at its highest: 144,360 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 6,373 MB. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

A region is not published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 46.174.55.78:28015.

What Rust version is recorded for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

The platform is Linux and the version is Rust network protocol 2635 and build 168909 on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. To join, your game must be on the same protocol; Steam handles the update.

Population

What player count is recorded on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

At the last refresh, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS recorded 2 players across 250 slots. Averaged across seven days, the player count is 1, with a peak of 6. Over the last 48 hours the busiest hour was 17:00 UTC, at an average of 3 players.

In the rankings, which position does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS hold?

Player hours over seven days place KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,200, within the top 14% of ranked servers. #237 against other trio servers.

Schedules

On KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, what does the data show for wipe day?

An average of 4 players was recorded at the busiest point of its recent wipes. At 40 hours after the latest wipe the crowd was at its peak. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.

Which times and days are wipes plotted at on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Its tag is followed for the prediction: too few of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's wipes are on record to confirm the schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The current world has been in use since 5 days 4 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Map and rules

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

The name records 2x gather for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Groups: 3 players maximum (trio). survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. Anti-cheat: VAC, from Valve, is on.

On which map is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS played?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs a procedural map of size 4,500 with seed 1337, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.

Filters

Where does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS appear among the Rust Graphs lists and filters?

On Rust Graphs, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is placed in these lists: Servers with a 2x gather rate, Modded Rust servers, Rust aim training servers, listed live and Trio Rust servers, plotted live. These filters on the server list return 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.

On KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, what is meant by each tag?

Tags published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp250 (Max players): 250 player slots; ts3 (Group limit): Team size is capped at 3; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded; jp0 (Custom tag): Set by the owner or a plugin, not by standard Rust; oxidation (Custom tag): Set by the owner or a plugin, not by standard Rust. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

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

Connect with client.connect 46.174.55.78:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. https://kaiman12rus.ru is its website.

NotesAnswered from the figures
Key

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 survival, as Rust plays.
mp250
Max players 250 player slots.
ts3
Group limit Team size is capped at 3.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it is listed under Modded.

Other

jp0
Custom tag Set by the owner or a plugin, not by standard Rust.
oxidation
Custom tag Set by the owner or a plugin, not by 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.

KeyTag string decoded