Rust Server TrendsSeismic network · station log
Recording Stations11,714 Players52,441 Active3,325 Wipes · 3 h137 48 h

Station XX-15589 · no signal

Kavkaz Rust X2 Trio | Hapis TEST

Offline 45.143.201.72:28015 checked 29d ago

2x moddedcarbon
Connect
Players now
1/ 5
20% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,589
top 65%
Last wipe
29d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-15589 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 5 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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. 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
15k10k15k20k20 Sep23 Sep26 Sep29 Sep2 Oct5 Oct

Top 65% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
0.6 daysbetween real wipes
on rhythm
40%of its recent wipes
wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

Mon 28 SepSun 27 SepSat 26 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Mon 28 Sep, 08:07 UTC29d ago M0.0steady 1 – running 1
Sun 27 Sep, 20:29 UTC30d ago M0.0steady 1 – 0.5 days 1
Sat 26 Sep, 09:39 UTC31d ago M0.0steady 1 – 1.5 days 1
Fri 25 Sep, 15:34 UTC32d ago M0.0rising 1 – 0.8 days 0
Fri 25 Sep, 08:00 UTC32d ago M0.0steady 1 – 0.3 days 1
Thu 24 Sep, 18:22 UTC33d ago M0.0rising 1 – 0.6 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
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 717 on average
421/ 500
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 537 on average
270/ 325
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 346 on average
214/ 250
Magic Rust #18 — Vanilla 2x | Pyccкий EU · groups of 150+ · 2x · weekly · 322 on average
10/ 100
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 322 on average
132/ 190
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 296 on average
160/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on Kavkaz Rust X2 Trio | Hapis TEST?

2x gather is what Kavkaz Rust X2 Trio | Hapis TEST runs, judging by its name. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on Kavkaz Rust X2 Trio | Hapis TEST right now?

No players are recorded on Kavkaz Rust X2 Trio | Hapis TEST at this moment; it is offline, and the last sighting was 29 days 12 hours ago.

How does Kavkaz Rust X2 Trio | Hapis TEST rank against other Rust servers?

On player hours for the past week, Kavkaz Rust X2 Trio | Hapis TEST sits at #15,589, which puts it inside the top 65% of every ranked server.

Server details

How reliably does Kavkaz Rust X2 Trio | Hapis TEST stay online?

No contact with Kavkaz Rust X2 Trio | Hapis TEST right now, and the last recorded contact was 29 days 12 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 17 September 2026.

Which region does Kavkaz Rust X2 Trio | Hapis TEST run from?

No region is published by Kavkaz Rust X2 Trio | Hapis TEST. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 45.143.201.72:28015.

What build of Rust does Kavkaz Rust X2 Trio | Hapis TEST use?

Kavkaz Rust X2 Trio | Hapis TEST is running Rust network protocol 2633 and build 165217 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on Kavkaz Rust X2 Trio | Hapis TEST?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does Kavkaz Rust X2 Trio | Hapis TEST run its wipes?

No next wipe can be predicted for Kavkaz Rust X2 Trio | Hapis TEST, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 29 days 12 hours.

Server tags

What do the server tags on Kavkaz Rust X2 Trio | Hapis TEST mean?

The game's server browser reads the tags Kavkaz Rust X2 Trio | Hapis TEST publishes: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): Slots: 5; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): It runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here; jp0 (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Kavkaz Rust X2 Trio | Hapis TEST appear?

You will find Kavkaz Rust X2 Trio | Hapis TEST on the following Rust Server Trends lists: 2x Rust servers, listed live and Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 2x.

Join the server

How do you connect to Kavkaz Rust X2 Trio | Hapis TEST?

You can connect by pressing F1 in Rust and typing client.connect 45.143.201.72: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.

Instrument codes

Server tags

what each one means

Published as mp5,ptrak,jp0,$r?,v2633,gmrust,cs165217,ts8,^z,^y

Game

gmrust
Game mode You'll find standard Rust survival here.
mp5
Max players Slots: 5.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build It runs game build 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon Carbon is the plugin framework running here.

Other

jp0
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.

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.