RUST METRICSFlight deck · live data
Data live Servers11,819 Players71,592 Populated3,741 Fresh wipes 3 h140 Scan5 min
‹ All servers88.99.1.43:28035
Online Full Queue Fresh wipe Wipe due No query

Alkad #3 (Max 2|Kits|Remove|TP)

Online EU 88.99.1.43:28035 checked 10m ago

duo biweekly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

last reading Tue 20: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 78 SERVER FPS

Server fps

48 h low 53 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 71,624 ×1000

Entities

48 h range 68,914–72,385 · memory 2,207 MB
1239 ET SINCE RESTART 15:49

Uptime

15 h 49 min since its last restart, at the last reading
7-day average1peak 4
Rank#3,811top 17% · #1409 in EU
Last wipe11d agobiweekly schedule
Next wipe2d 13hFri 30 Oct, 11:02 UTC
Memory2,207MB48 h peak 2 players
REC 1

Players

AveragePeak
00.511.5222:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020022:0007:0016:0002:0011:0020: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 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 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 17% of all ranked servers, top 48% in EU, and #223 of the duo servers (top 53%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 11:02 UTC, in 2d 13h. Every other Friday at 11:02 UTC · medium confidence

usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 3.5

Coming wipes

  1. WPT 1Fri 30 Oct, 11:02 UTC2d 13h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 21hFW
  3. WPT 3Fri 13 Nov, 11:02 UTC16d 13h
  4. WPT 4Fri 27 Nov, 11:02 UTC30d 13h
  5. WPT 5Thu 3 Dec, 19:00 UTC36d 21hFW
  6. WPT 6Fri 11 Dec, 11:02 UTC44d 13h

The first 48 hours of its last wipes

Fri 16 OctFri 2 OctFri 18 Sep
02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 11:02 UTC11d ago 3 – running 0
Fri 2 Oct, 11:00 UTC25d ago 6 halved by day 6 14 days 0
Fri 18 Sep, 11:01 UTC39d ago 5 halved by day 1 14 days 1

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 Alkad #3 (Max 2|Kits|Remove|TP)?

The busiest point of its recent wipes drew 5 players on average. 30 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. When it didn't hold, by day 3.5 it fell below half.

How often does Alkad #3 (Max 2|Kits|Remove|TP) wipe, and when?

The wipe rhythm of Alkad #3 (Max 2|Kits|Remove|TP) is every other Friday at 11:02 UTC. Due on Friday 30 October at 11:02 UTC is its next wipe. 11 days 10 hours ago the current world was made. Its tags publish a wipe schedule of one wipe every two weeks.

Tag meanings

How should you read the tags on Alkad #3 (Max 2|Kits|Remove|TP)?

Tags published by Alkad #3 (Max 2|Kits|Remove|TP), read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts2 (Group limit): Team cap: 2; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Two-week wipe schedule; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game; EU (Europe): The server browser files it under Europe. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Alkad #3 (Max 2|Kits|Remove|TP) appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Alkad #3 (Max 2|Kits|Remove|TP): Duo Rust servers, EU Rust servers, checked and Modded Rust servers, checked live. Reading: server list filters. It comes up under Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Player count

Where does Alkad #3 (Max 2|Kits|Remove|TP) sit in the rankings?

Top 17% of all ranked servers: Alkad #3 (Max 2|Kits|Remove|TP) takes #3,811 on seven-day player hours and #1,409 in Europe. The duo group places it at #223.

How full does Alkad #3 (Max 2|Kits|Remove|TP) get?

Current headcount on Alkad #3 (Max 2|Kits|Remove|TP): 0 players, 100 slots available. Seven-day check: 1 players on average. Peak reading: 4. The last 48 hours peaked at 19:00 UTC, averaging 2 players at that hour.

Operator and location

Where does Alkad #3 (Max 2|Kits|Remove|TP) sit?

Reading: location. The EU tag puts Alkad #3 (Max 2|Kits|Remove|TP) in Europe. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 88.99.1.43:28035.

What Rust version is Alkad #3 (Max 2|Kits|Remove|TP) on?

Rust network protocol 2635 and build 168909 on Windows is the build Alkad #3 (Max 2|Kits|Remove|TP) runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for Alkad #3 (Max 2|Kits|Remove|TP)?

Reading: 79 server fps on average across the last 48 hours. It never dropped below 53. Reading: 72,385 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 3,030 MB. Expect lag when fps falls and entities climb.

How reliable is Alkad #3 (Max 2|Kits|Remove|TP), and is it online now?

Alkad #3 (Max 2|Kits|Remove|TP) reports online. Status: normal. By its reported uptime, the last restart was roughly 15 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

What settings and rules apply on Alkad #3 (Max 2|Kits|Remove|TP)?

Reading the name gives no gather rate for Alkad #3 (Max 2|Kits|Remove|TP). The group cap is 2 players, read as duo. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. VAC is on. That is Valve's anti-cheat.

What map is Alkad #3 (Max 2|Kits|Remove|TP) on?

Check: map. Procedural, size 3,500, seed 1472934234, generated by the game on Alkad #3 (Max 2|Kits|Remove|TP). View it on RustMaps from this page: matching size and seed give an identical map.

Join

How do you connect to Alkad #3 (Max 2|Kits|Remove|TP)?

Press F1 in Rust and enter client.connect 88.99.1.43:28035. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://m.vk.com/rust_alkad is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts2,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts2
Group limit Team cap: 2.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Two-week wipe schedule.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

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

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.