Rust Server TrendsSeismic network · station log
Recording Stations11,748 Players75,412 Active3,731 Wipes · 3 h136 48 h

Station EU-5418 · recording

KIPISH |X2|WIPE(27.10)

Online EU 5.42.211.31:35367 checked 12m ago

2x biweekly wipes moddedcarbon
Connect
Players now
0/ 100
0% full
Motion · 24 h
M0.1rising
+1 players on the day
7-day average
0
peak 4
Rank
#5,418
top 24% · #1778 in EU
Last wipe
17h ago
biweekly schedule
Next wipe
8d 5h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station EU-5418 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 100 slots
Motion · 24 h
M0.1rising+1 players
Sharpest hour
+2into Wed 10:00 UTC
Peak · 48 h
4most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
0123414:0023:0008:0018:0003:0012:00Wiped Tue 27 Oct, 19:52 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
020040060080014:0023:0008:0018:0003:0012:00Wiped Tue 27 Oct, 19:52 UTCWIPE

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 17 Sep. 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
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 24% of all ranked servers, top 61% in EU. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

a steady gap

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

usual gap
12.1 daysbetween real wipes
on rhythm
100%of its recent wipes
wipe-day peak
8players, last three wipes
crowd held
0%else halves by day 3

Coming wipes

  1. 8d 5hThu 5 Nov, 19:00 UTCFW
  2. 11d 9hSun 8 Nov, 23:26 UTC
  3. 23d 13hSat 21 Nov, 03:00 UTC
  4. 36d 5hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Tue 13 OctThu 1 OctSun 20 Sep
02.557.510+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 20 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 27 Oct, 19:52 UTC17h ago – – – – running 0
Tue 13 Oct, 21:41 UTC14d ago M0.7rising 5 halved by day 2 13.9 days 0
Thu 1 Oct, 18:07 UTC FW26d ago M0.8rising 7 halved by day 6 12.1 days 0
Sun 20 Sep, 17:33 UTC37d ago M1.0rising 11 halved by day 3 11 days 2

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 Medium | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · biweekly · 208 on average
39/ 100
Magic Rust #22 — Vanilla 2x (Biweekly) | Pyccкий EU · groups of 150+ · 2x · biweekly · 53 on average
27/ 200
ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10 EU · groups of 10+ · 2x · biweekly · 50 on average
51/ 200
PROSTOJ #6 | Ресурсы x2 | Компоненты x1 EU · groups of 8+ · 2x · biweekly · 48 on average
34/ 200
Vital Rust - EU Medium | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · biweekly · 41 on average
6/ 75
РОССИЙСКИЙ x2 | GGRust #5 | Для нoвичкoв 2x EU · groups of 300+ · 2x · biweekly · 36 on average
15/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on KIPISH |X2|WIPE(27.10)?

The procedural map on KIPISH |X2|WIPE(27.10) is size 4,500 with seed 1337, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map. Its map carries the name Custom Map.

Which settings and rules apply on KIPISH |X2|WIPE(27.10)?

Going by its name, KIPISH |X2|WIPE(27.10) runs 2x gather. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on KIPISH |X2|WIPE(27.10)?

0 of the 100 slots on KIPISH |X2|WIPE(27.10) are filled right now. The seven-day average is 0 players, with a peak of 4. The busiest point in the last 48 hours came at 10:00 UTC, averaging 4 players.

How does KIPISH |X2|WIPE(27.10) rank against other Rust servers?

For player hours across the last seven days, KIPISH |X2|WIPE(27.10) takes #5,418 overall and #1,778 in Europe, inside the top 24% of all ranked servers.

Server details

How reliably does KIPISH |X2|WIPE(27.10) stay online?

Right now, you can reach KIPISH |X2|WIPE(27.10). Going by the uptime figure it reports, it restarted about 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. 13 September 2026 is when Rust Server Trends first recorded it.

Does KIPISH |X2|WIPE(27.10) hold a steady tick rate?

Its average server fps over the last 48 hours was 311, and it never dropped below 131. At its highest, it carried 97,796 entities: buildings, deployables and the world's other contents. Its highest memory use was 3,357 MB. Low fps together with a growing entity count is what players experience as lag.

Where in the world is KIPISH |X2|WIPE(27.10) hosted?

The EU tag is how KIPISH |X2|WIPE(27.10) lists itself in Europe. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 5.42.211.31:35367.

What build of Rust does KIPISH |X2|WIPE(27.10) use?

Rust network protocol 2635 and build 168909 on Windows is what KIPISH |X2|WIPE(27.10) runs. 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 KIPISH |X2|WIPE(27.10)?

On average, the busiest point of its recent wipes drew 8 players. The peak on the most recent wipe came 20 hours after the wipe. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 3.

On what timetable does KIPISH |X2|WIPE(27.10) run its wipes?

The recent gap between wipes at KIPISH |X2|WIPE(27.10) is about 12.1 days. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 17 hours. Its tags state that it wipes every two weeks.

Tags

What do the server tags on KIPISH |X2|WIPE(27.10) mean?

These are the tags KIPISH |X2|WIPE(27.10) publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here; EU (Europe): In the server browser it appears under Europe. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does KIPISH |X2|WIPE(27.10) appear?

The Rust Server Trends lists that take in KIPISH |X2|WIPE(27.10) are: 2x Rust servers, listed live, EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours; Gather rate: 2x.

Join the server

What steps get you onto KIPISH |X2|WIPE(27.10)?

To join, enter client.connect 5.42.211.31:35367 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://t.me/+s7a26cRawSAyZWZi.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^z,^y,^b,EU,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players 100 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly A wipe comes every second week.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

Region

EU
Europe In the server browser it appears under Europe.

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.