RUST METRICSFlight deck · live data
Data live Servers11,872 Players96,217 Populated4,094 Fresh wipes 3 h158 Scan5 min
‹ All servers46.174.55.78:28015
Online Full Queue Fresh wipe Wipe due No query

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS

Online 46.174.55.78:28015 checked 10m ago

2x trio biweekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Tue 16:00 UTC
0 62 125 188 250 PAX 3 /250

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 89 SERVER FPS

Server fps

48 h low 60 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 142,215 ×1000

Entities

48 h range 123,470–144,029 · memory 5,228 MB
1239 ET SINCE RESTART 01:05

Uptime

1 h 5 min since its last restart, at the last reading
7-day average1peak 6
Rank#3,115top 14%
Last wipe4d agobiweekly schedule
Next wipe9d 0hThu 5 Nov, 19:00 UTC FW
Memory5,228MB48 h peak 4 players
REC 1

Players

AveragePeak
0123419:0004:0013:0022:0007:0016:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020019:0004:0013:0022:0007:0016: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct12 Oct16 Oct19 Oct23 Oct27 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 9d 0h. 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. WPT 1Thu 5 Nov, 19:00 UTC9d 0hFW
  2. WPT 2Fri 6 Nov, 16:54 UTC9d 22h
  3. WPT 3Fri 20 Nov, 16:54 UTC23d 22h
  4. WPT 4Thu 3 Dec, 19:00 UTC37d 0hFW
  5. WPT 5Fri 4 Dec, 16:54 UTC37d 22h

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.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

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

An average of 4 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 40 hours. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS follow?

The prediction follows its tag, because too few of KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 4 days 1 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

Which tags does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS carry, and what do they mean?

Tags published by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp250 (Max players): Slots: 250; ts3 (Group limit): Teams are capped at 3; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^b (Biweekly): Two-week wipe schedule; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; jp0 (Custom tag): Owner or plugin definition: this tag is not a standard Rust one; oxidation (Custom tag): Owner or plugin definition: this tag is not a standard Rust one. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Rust Metrics lists featuring KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: 2x Rust servers, checked live, Modded Rust servers, checked live, Aim training servers, live readings and Trio servers, group limit 3. 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.

Player count

What position does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS hold among Rust servers?

Player hours over seven days put KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS at #3,115, in the top 14% of all ranked servers. The trio group places it at #232.

How full does KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS get?

Current headcount on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS: 3 players, 250 slots available. Seven-day check: 1 players on average. Peak reading: 6. Average at the busiest hour was 3 players, at 16:00 UTC over the last 48 hours.

Server

What location is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS hosted in?

Reading: location. KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.174.55.78:28015.

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

Version check: Rust network protocol 2635 and build 168909 on Linux, run by KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. To get in, your game needs the same protocol; Steam applies the update.

What is the performance reading for KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Reading: 80 server fps on average across the last 48 hours. It never dropped below 60. Reading: 144,029 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 6,373 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS, and is it online?

KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 1 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 8 October 2026, recorded by Rust Metrics.

Rules and settings

How is KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS configured, and what rules are in force?

The name carries the rate: 2x gather on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. Check: group limit. 3 players, under the name trio. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

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

Check: map. Procedural, size 4,500, seed 1337, generated by the game on KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

Join

What do you do to join KAIMAN RUST | X2 | MAX3 | EVENTS | QUESTS?

Press F1 in Rust and enter client.connect 46.174.55.78:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://kaiman12rus.ru.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp250
Max players Slots: 250.
ts3
Group limit Teams are capped at 3.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Other

jp0
Custom tag Owner or plugin definition: this tag is not a standard Rust one.
oxidation
Custom tag Owner or plugin definition: this tag is not a standard Rust one.

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.