RUST METRICSFlight deck · live data
Data live Servers11,618 Players39,799 Populated2,961 Fresh wipes 3 h88 Scan5 min
‹ All servers5.42.211.31:35367
Online Full Queue Fresh wipe Wipe due No query

KIPISH |X2|WIPE(27.10)

Online EU 5.42.211.31:35367 checked 9m ago

2x biweekly wipes moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 06:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

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

Server fps

48 h low 62 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 96,703 ×1000

Entities

48 h range 60,530–98,540 · memory 3,208 MB
1239 ET SINCE RESTART 09:02

Uptime

9 h 2 min since its last restart, at the last reading
7-day average0peak 4
Rank#4,987top 22% · #1702 in EU
Last wipe1d agobiweekly schedule
Next wipe7d 11hThu 5 Nov, 19:00 UTC FW
Memory3,208MB48 h peak 4 players
REC 1

Players

AveragePeakWipe
0123408:0017:0002:0011:0021:0006:00Wiped Tue 27 Oct, 19:52 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
020040060080008:0017:0002:0011:0021:0006: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.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

a steady gap

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

usual gap12.1 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak8players, last three wipes
crowd held0%else halves by day 3

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 11hFW
  2. WPT 2Sun 8 Nov, 23:26 UTC10d 15h
  3. WPT 3Sat 21 Nov, 03:00 UTC22d 19h
  4. WPT 4Thu 3 Dec, 19:00 UTC35d 11hFW

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 19:52 UTC1d ago – – running 0
Tue 13 Oct, 21:41 UTC15d ago 5 halved by day 2 13.9 days 0
Thu 1 Oct, 18:07 UTC FW27d ago 7 halved by day 6 12.1 days 0
Sun 20 Sep, 17:33 UTC38d ago 11 halved by day 3 11 days 2

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

Reset cycle

What should you expect from wipe day on KIPISH |X2|WIPE(27.10)?

At their busiest, its recent wipes drew 8 players on average. Peak crowd on the latest wipe: 20 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 3 when it didn't.

What wipe timing does KIPISH |X2|WIPE(27.10) follow?

The recent wipe interval on KIPISH |X2|WIPE(27.10) is about 12.1 days. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was made 35 hours ago. Its tags publish a wipe schedule of one wipe every two weeks.

Lists and filters

How should you read the tags on KIPISH |X2|WIPE(27.10)?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon; EU (Europe): The server browser files it under Europe from KIPISH |X2|WIPE(27.10). 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 KIPISH |X2|WIPE(27.10)?

These Rust Metrics lists carry KIPISH |X2|WIPE(27.10): 2x Rust servers, checked live, EU Rust servers, checked and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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 3 days; Gather rate: 2x.

Population

Where does KIPISH |X2|WIPE(27.10) sit in the rankings?

Player hours over the last seven days put KIPISH |X2|WIPE(27.10) at #4,987, #1,702 in Europe, in the top 22% of all ranked servers.

What player count does KIPISH |X2|WIPE(27.10) carry?

Current headcount on KIPISH |X2|WIPE(27.10): 0 players, 100 slots available. Check: players over seven days. Average 0, peak 4. The last 48 hours peaked at 10:00 UTC, averaging 4 players at that hour.

Operator and location

Where does KIPISH |X2|WIPE(27.10) sit?

Its EU tag places KIPISH |X2|WIPE(27.10) in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 5.42.211.31:35367.

What Rust version is KIPISH |X2|WIPE(27.10) on?

Reading: KIPISH |X2|WIPE(27.10), Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for KIPISH |X2|WIPE(27.10)?

Check: fps. Average 267 server fps over the last 48 hours, low of 62. Within range. Peak entity count: 98,540. Buildings, deployables and all else included. Memory peak: 3,529 MB. Expect lag when fps falls and entities climb.

Is KIPISH |X2|WIPE(27.10) up, and how often does it stay up?

Check: connection. KIPISH |X2|WIPE(27.10) is online at this moment. Check: restart. The uptime it reports puts the last restart about 9 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What rules does KIPISH |X2|WIPE(27.10) enforce, and what are its settings?

The name carries the rate: 2x gather on KIPISH |X2|WIPE(27.10). 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is KIPISH |X2|WIPE(27.10) on?

Size 4,500 and seed 1337: the game generates the procedural map on KIPISH |X2|WIPE(27.10) from them. 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 KIPISH |X2|WIPE(27.10)?

Check: join. Open Rust, press F1, then enter client.connect 5.42.211.31:35367. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://t.me/+s7a26cRawSAyZWZi.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: Carbon.

Region

EU
Europe The server browser files it 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.