Rust Server TrendsSeismic network · station log
Recording Stations11,644 Players39,508 Active2,969 Wipes · 3 h74 48 h

Station XX-3103 · recording

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

Online 46.174.55.78:28015 checked 10m ago

2x trio biweekly wipes moddedoxide
Connect
Players now
0/ 250
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 6
Rank
#3,103
top 14%
Last wipe
4d ago
biweekly schedule
Next wipe
8d 16h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-3103 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 250 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+2into Tue 15:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123403:0012:0021:0007:0016:0001:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020003:0012:0021:0007:0016:0001: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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct20 Oct24 Oct28 Oct

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

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 8d 16h. The force wipe · high confidence

usual gap
6.4 daysbetween real wipes
on rhythm
67%of its recent wipes
wipe-day peak
4players, last three wipes
crowd held
100%of its cycles kept half the crowd

Coming wipes

  1. 8d 16hThu 5 Nov, 19:00 UTCFW
  2. 9d 13hFri 6 Nov, 16:54 UTC
  3. 23d 13hFri 20 Nov, 16:54 UTC
  4. 36d 16hThu 3 Dec, 19:00 UTCFW
  5. 37d 13hFri 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 16:54 UTC4d ago M0.8rising 6 – running 0
Fri 16 Oct, 15:22 UTC11d ago M0.3rising 3 held half 7.1 days 1
Thu 15 Oct, 09:09 UTC12d ago M0.5rising 3 – 1.3 days 0
Thu 8 Oct, 23:23 UTC19d ago M0.5rising 3 held half 6.4 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] FULLWIPED 25.10 trio · 2x · biweekly · 137 on average
11/ 200
HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED NA · trio · 2x · biweekly · 10 on average
21/ 150
HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPED EU · trio · 2x · biweekly · 3 on average
1/ 150
ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ] EU · trio · 2x · biweekly · 2 on average
0/ 150
1/ 150
#3 [RU] ДЛЯ НОВИЧКОВ X2|MAX3|ORP|SHOP|R7ZONE.RU EU · trio · 2x · biweekly · 1 on average
0/ 300
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs a procedural map of size 4,500 with seed 1337, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. You will find the map named Custom Map.

Which settings and rules apply on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

2x gather is what KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs, judging by its name. 3 players is the most a group can hold (trio). survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Live population

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

At this moment, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS records 0 players across 250 slots. The seven-day average is 1 players, with a peak of 6. Averaged over the last 48 hours, the busiest hour was 16:00 UTC at 3 players.

How does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS rank against other Rust servers?

The last seven days of player hours place KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,103, in the top 14% of all ranked servers. Within trio, it places #233.

Server facts

How reliably does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS stay online?

As recorded now, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is running. Its reported uptime points to a restart about 10 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 8 October 2026.

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

Across the last 48 hours it averaged 81 server fps, with a floor of 60. The world held up to 144,029 entities at its peak, buildings and deployables included. Its highest memory use was 6,373 MB. What you feel as lag is the combination of low fps and a rising entity count.

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

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

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

Rust network protocol 2635 and build 168909 on Linux is what KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

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

The recent wipes averaged a busiest count of 4 players. 40 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.

On what timetable does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS run its wipes?

The prediction is taken from its tag, since KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS has too few wipes 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. 4 days 10 hours is how long the current world has been running. Every two weeks it wipes, according to the schedule in its tags.

Tags

What do the server tags on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS mean?

The game's server browser reads the tags KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS publishes: gmrust (Game mode): You'll find standard Rust survival here; mp250 (Max players): The server has 250 slots; ts3 (Group limit): Each team can hold up to 3; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^b (Biweekly): The wipe cycle is two weeks; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; jp0 (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust; oxidation (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS appear?

These Rust Server Trends lists include KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: 2x Rust servers, listed live, Modded Rust servers, tracked live, Rust aim training servers, live and Best trio Rust servers. These filters bring it up 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 to join

What steps get you onto KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

You can connect by pressing F1 in Rust and typing client.connect 46.174.55.78:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://kaiman12rus.ru is where its website lives.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp250
Max players The server has 250 slots.
ts3
Group limit Each team can hold up to 3.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Other

jp0
Custom tag The owner or a plugin applied this tag, which isn't part of standard Rust.
oxidation
Custom tag The owner or a plugin applied this tag, which isn't part of 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.