Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO P SRV11,858online PAX85,113playing OCC3,958with players WIPED 3H170
MODModded traffic
Callsign

KMN3105=

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

Online 46.174.55.78:28015 checked 12m ago

2x trio biweekly wipes moddedoxide
Clearance · join
Players now 1/ 250 0% full
7-day average1peak 6
Rank#3,105top 14%
Last wipe4d agobiweekly schedule
Next wipe8d 22hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeak
0123421:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

05010015020021:0006:0015:0001:0010:0019: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 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.

Flight plan

Wipe schedule

from its schedule tag
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h.

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

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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign SRV015trio · 2x · biweekly · 137 on average SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] FULLWIPED 25.10
    Players 55/200
  2. 02MOD
    Callsign HLL010NA · trio · 2x · biweekly · 10 on average HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPED
    Players 7/150
  3. 03MOD
    Callsign HLL010EU · trio · 2x · biweekly · 3 on average HollowServers.co EU 2x Solo/Duo |X2 JUST FULL WIPED
    Players 4/150
  4. 04MOD
    Callsign MAX210EU · trio · 2x · biweekly · 2 on average ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ]
    Players 1/150
  5. 05MOD
    Callsign PRJ014trio · 2x · biweekly · 1 on average » ProjectGaming.gg | 2X Vanilla | Solo/Duo/Trio | WIPED 10/25
    Players 5/150
  6. 06MOD
    Callsign ORP027EU · trio · 2x · biweekly · 1 on average #3 [RU] ДЛЯ НОВИЧКОВ X2|MAX3|ORP|SHOP|R7ZONE.RU
    Players 0/300
ATIS · this server

Quick answers

From the figures on this page.

Filters

Where does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS appear in Rust Tracker lists and filters?

2x Rust servers, tracked live, Modded servers, tracked live, Combat training servers, tracked live and Trio Rust servers, tracked live — the Rust Tracker lists that include KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. It comes up 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 tags on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Listed for the server browser to read, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS publishes these tags: gmrust (Game mode): Rust survival, standard mode; mp250 (Max players): Capacity: 250 slots; ts3 (Group limit): Team limit: 3; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): No region code is set; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; jp0 (Custom tag): The owner or a plugin set it; it is not a standard Rust tag; oxidation (Custom tag): The owner or a plugin set it; it is not a standard Rust tag. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Times

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

The average peak across recent wipes: 4 players. The peak on the latest wipe came 40 hours after it. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

When does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS wipe?

The schedule of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS cannot be confirmed, with too few wipes on record: the prediction follows its tag. On Thursday 5 November at 19:00 UTC the force wipe lands, its next wipe, and every Rust server wipes with it. 4 days 3 hours since this world was made. Its tags carry an every-two-weeks wipe schedule.

Location and Status

Is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS up, and how does its uptime hold?

Tracking shows KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS online as of now. About 4 hours ago it restarted last, based on reported uptime. Uptime stood at 100% for the last 7 full days, 168 of 168 hours online. The first sighting by Rust Tracker was 8 October 2026.

Which Rust build 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. The same protocol is required to join, and Steam updates it for you.

Is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS holding performance?

For the last 48 hours it averaged 80 server fps; the floor was 60. Buildings, deployables and the rest of the world took it to a maximum of 144,029 entities. It drew as much as 6,373 MB of memory. Players feel lag when fps drops and the entity count climbs.

Which location is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS in?

Region: none published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 46.174.55.78:28015.

Population

How many players are on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS right now?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is at 1 players, capacity 250. Over seven days: average 1, peak 6 players. Busiest window in 48 hours: 16:00 UTC, 3 players on average.

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

Seven-day player hours put KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,105, within the top 14% of all ranked servers. Position #233 among trio servers.

Map and Rules

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

2x gather is what KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS runs, going by its name. The cap sits at 3 players for a group (trio). It runs survival, gather, build and raid: the standard game. Fighting and raiding between players are on. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

Which map is confirmed for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Generated by the game from seed 1337, the procedural map on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS measures 4,500. Size and seed match, so the map is the same: view it on RustMaps from this page. Its map goes by the name Custom Map.

How to Join

Which steps join KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Open the console in Rust with F1 after starting the game, then type client.connect 46.174.55.78:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://kaiman12rus.ru.

Transponder 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 Rust survival, standard mode.
mp250
Max players Capacity: 250 slots.
ts3
Group limit Team limit: 3.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the network layer — the game's standard.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Every two weeks it wipes.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

Other

jp0
Custom tag The owner or a plugin set it; it is not a standard Rust tag.
oxidation
Custom tag The owner or a plugin set it; it is not a standard Rust tag.

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.