Skip to the page
RUST ANALYTICS
LIVE78,385PLY11,749SRV
QUOTE 46.174.55.78:28015 Online checked 10m ago

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

2x trio biweekly wipes moddedoxide
Players · last
0/ 100
−1−100.0%24h
0% full
Day range 0 2
7-day avg 1 peak 5
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join

Key statistics

the figures behind the quote
Players now
0/ 100
0% full
Change · 24h
−1
−100.0% from 1
7-day average
1
peak 5
Rank
#4,140
top 18%
Rank · 7d ago
–
not ranked a week ago
Last wipe
4d ago
biweekly schedule
Next wipe
9d 3h
Thu 22 Oct, 23:23 UTC
Group limit
trio
players per team
Gather rate
2x
read from the name
Score
92
player hours, last seven days
Map
3500
Procedural Map · seed 125874
First seen
8 Oct 2026
no hostname published

Players

AveragePeak
00.511.5221:0006:0015:0000:0009:0018:00

Hourly average and peak, UTC. Busiest hour of the two days: 2 players.

Server performance

05010015020021:0006:0015:0000:0009:0018: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 Oct9 Oct10 Oct11 Oct12 Oct13 Oct

Top 18% of all ranked servers, and #294 of the trio servers (top 49%). Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag
Next wipeThursday 22 October, 23:23 UTCin 9d 3h

Its biweekly schedule tag · low confidence

wipe-day peak
3
players, last three wipes

Coming wipes

  1. 9d 3hThu 22 Oct, 23:23 UTC
  2. 22d 22hThu 5 Nov, 19:00 UTCFW
  3. 37d 3hThu 19 Nov, 23:23 UTC

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 19 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 23:23 UTC4d ago 3 – running 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
#ServerLastChg 24hPlayers over the last 24 hours24h
1SURVIVORS.GG #3 [ 2x Solo/Duo/Trio ] FULLWIPED 11.10trio · 2x · biweekly · 138 on average76/200−79−50.9%
2HollowServers.co 2x Solo/Duo |X2 JUST FULL WIPEDNA · trio · 2x · biweekly · 11 on average7/150−9−55.8%
3#3 [RU] ДЛЯ НОВИЧКОВ X2|MAX3|ORP|SHOP|R7ZONE.RUEU · trio · 2x · biweekly · 6 on average1/300+1
4ПРОСТОЙ #1 MAX3 [X2|ДЛЯ НОВИЧКОВ]EU · trio · 2x · biweekly · 2 on average4/50+2+77.8%
5CODIGO ROJO x2 | LATAM/US | SOLO/DUO/TRIO | NO RAID OFF | ACTIVNA · trio · 2x · biweekly · 1 on average0/40−2−100.0%
6[AU] Winterust - 2x Small Solo/Duo/Trio |2500 Map|BP ShareOC · trio · 2x · biweekly · 1 on average0/75+0

Quick answers

from the figures on this page

Map and Rules

What settings and rules are in place on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

A gather rate of 2x appears in the name of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. The group limit is 3 players, set via trio. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Oxide. VAC is active.

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

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS uses a procedural map of size 3,500 with seed 125874, generated by the game. You can see the map on RustMaps from this page, as the same size and seed give the same map.

Population

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

In the top 18% of all ranked servers, KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is #4,140 on player hours over the last seven days. Among servers in trio, it stands at #294.

How many players does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS have?

0 of 100 slots on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS are filled at the moment. Average players over seven days: 1; peak: 5. At 15:00 UTC in the last 48 hours, it averaged 2 players, the busiest hour.

Wipe Schedule

How does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS handle wipe day?

Recent wipes at this server drew an average peak of 3 players. 19 hours after the latest wipe, the crowd reached its peak.

How often does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS wipe?

Its tag guides the prediction, as KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS has too few wipes on record to confirm its schedule. On Thursday 22 October at 23:23 UTC the next wipe is due. 4 days 20 hours ago the current world was created. Its tags carry a wipe schedule of every two weeks.

Server Overview

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

No region is published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 46.174.55.78:28015 is its address.

How is the performance on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Average server fps for the last 48 hours is 53; the floor was 10. At its peak it held 76,649 entities: buildings, deployables and the rest of the world. Up to 5,037 MB of memory was used. Low fps and growing entities are the source of felt lag.

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS is on which Rust version?

The build is Rust network protocol 2634 and build 167398 on Linux, running on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Your game needs the same protocol to get in; Steam takes care of the update.

Is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS up, and how consistent is its uptime?

Online at this moment: KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Its own uptime figure dates the last restart to roughly 4 hours ago. 100% is its uptime for the last 4 full days, 96 of 96 hours. The earliest Rust Analytics saw it was 8 October 2026.

Server Tags

What is the meaning of the tags on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

These tags are published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp100 (Max players): It holds 100 slots; ts3 (Group limit): Teams take no more than 3; v2634 (Protocol): To join, your game needs protocol 2634; cs167398 (Build): Game build: 167398; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe cycle; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; jp0 (Custom tag): The owner or a plugin added this; it is not part of the standard Rust tag set; oxidation (Custom tag): The owner or a plugin added this; it is not part of the standard Rust tag set. Also in the tags and at the top of this page: current players, queue and world creation time.

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

The following Rust Analytics lists feature KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: 2x Rust servers, Modded Rust servers, Rust aim training servers and Trio Rust servers. It appears 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.

Joining the Server

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

The console route: start Rust, press F1, enter client.connect 46.174.55.78:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.

Server tags

what each one means

Published as mp100,ptrak,jp0,$r?,v2634,^b,gmrust,cs167398,ts3,^o^z,oxidation

Game

gmrust
Game mode Rust's standard survival mode.
mp100
Max players It holds 100 slots.
ts3
Group limit Teams take no more than 3.
v2634
Protocol To join, your game needs protocol 2634.
cs167398
Build Game build: 167398.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Two-week wipe cycle.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) is in use.
^z
Modded Categorised as Modded: plugins or settings alter gameplay.

Other

jp0
Custom tag The owner or a plugin added this; it is not part of the standard Rust tag set.
oxidation
Custom tag The owner or a plugin added this; it is not part of the standard Rust tag set.

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.