Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO H SRV11,872online PAX102,993playing OCC3,951with players WIPED 3H555
MODModded traffic
Callsign

ALK4408=

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

Online EU 88.99.1.43:28035 checked 12m ago

duo biweekly wipes vanillamoddedoxide
Clearance · join
Players now 0/ 100 0% full
7-day average0peak 3
Rank#4,408top 20% · #1579 in EU
Last wipe13d agobiweekly schedule
Next wipe15hFri 30 Oct, 11:02 UTC
Track history

Players

AveragePeak
00.511.5220:0005:0014:0000:0009:0018:00

Hourly average and peak, UTC.

Server performance

05010015020020:0005:0014:0000:0009:0018: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.

Rank

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

Top 20% of all ranked servers, top 54% in EU, and #240 of the duo servers (top 57%). Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

fixed weekdays
ETD · next wipe

Next wipe Friday 30 October, 11:02 UTC, in 15h.

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. 15hFri 30 Oct, 11:02 UTC
  2. 6d 23hThu 5 Nov, 19:00 UTCFW
  3. 14d 15hFri 13 Nov, 11:02 UTC
  4. 28d 15hFri 27 Nov, 11:02 UTC
  5. 34d 23hThu 3 Dec, 19:00 UTCFW
  6. 42d 15hFri 11 Dec, 11:02 UTC

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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 11:02 UTC13d ago 3 – running 0
Fri 2 Oct, 11:00 UTC27d ago 6 halved by day 6 14 days 0
Fri 18 Sep, 11:01 UTC41d 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01COM
    Callsign RST028EU · duo · biweekly · 89 on average RustOps - Solo/Duo | FULLWIPE 29/10 29.10 10/29
    Players 257/425
  2. 02COM
    Callsign ENJ025EU · duo · biweekly · 36 on average Enjoy - Solo/Duo only, no BP wipes. True Vanilla.
    Players 210/400
  3. 03COM
    Callsign DUO010EU · duo · biweekly · 11 on average Московский Duo/Solo | Для новичков
    Players 11/100
  4. 04COM
    Callsign PLR086EU · duo · biweekly · 3 on average POLAR - EU Solo/Duo | Biweekly | No BP Wipes 10/29 29.10
    Players 5/125
  5. 05COM
    Callsign EUR546EU · duo · biweekly · 1 on average EU Rust for Solo's/Duo's BiWeekly Noob Friendly
    Players 2/40
  6. 06COM
    Callsign RST017EU · duo · biweekly · 1 on average Rustafied- EU Solo/Duo | Biweekly | No BP Wipes 29/10 12.11
    Players 0/100
ATIS · this server

Quick answers

From the figures on this page.

Tags

Which lists and filters on Rust Tracker show Alkad #3 (Max 2|Kits|Remove|TP)?

On Rust Tracker, Alkad #3 (Max 2|Kits|Remove|TP) sits in these lists: Duo servers: group limit 2, EU Rust servers, tracked live and Modded servers, tracked live. It comes up under these filters on the server list: 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.

What do the tags mean that Alkad #3 (Max 2|Kits|Remove|TP) is listed under?

Listed for the server browser to read, Alkad #3 (Max 2|Kits|Remove|TP) publishes these tags: gmrust (Game mode): Standard survival mode for Rust; mp100 (Max players): 100 slots on this server; ts2 (Group limit): No team may exceed 2; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^b (Biweekly): Two-week wipe cycle; ^v (Vanilla): Facepunch's game unaltered: rates, kits and rules unchanged; ^o (Oxide): A plugin framework runs here: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; EU (Europe): In the server browser it is listed under Europe. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

What should you expect on Alkad #3 (Max 2|Kits|Remove|TP) when wipe day lands?

At their busiest, recent wipes averaged 5 players. The peak on the latest wipe came 30 hours after it. The crowd stayed above half the peak until the next wipe in 0% of recent wipes. By day 3.5 the crowd dropped below half where it did not hold.

Which wipe times are confirmed for Alkad #3 (Max 2|Kits|Remove|TP)?

Wipe rhythm at Alkad #3 (Max 2|Kits|Remove|TP): every other Friday at 11:02 UTC. Friday 30 October at 11:02 UTC is when the next wipe falls due. This world has been running 13 days 8 hours. A two-weekly wipe schedule is published in its tags.

Location and Status

Is Alkad #3 (Max 2|Kits|Remove|TP) up, and how does its uptime hold?

Tracking shows Alkad #3 (Max 2|Kits|Remove|TP) online as of now. About 13 hours ago it restarted last, based on reported uptime. 167 of 168 hours up over the last 7 full days: 99% uptime. Rust Tracker logged it first on 13 September 2026.

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

Rust network protocol 2635 and build 168909 on Windows is what Alkad #3 (Max 2|Kits|Remove|TP) runs. The same protocol is required to join, and Steam updates it for you.

How smoothly does Alkad #3 (Max 2|Kits|Remove|TP) run?

Average server fps over the last 48 hours: 78, with a low of 41. Peak entity count: 71,627, covering buildings, deployables and all else in the world. Peak memory use: 3,009 MB. Players feel lag when fps drops and the entity count climbs.

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

In Europe, under its EU tag, is where Alkad #3 (Max 2|Kits|Remove|TP) lists itself. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 88.99.1.43:28035.

Player Count

Is Alkad #3 (Max 2|Kits|Remove|TP) busy?

Alkad #3 (Max 2|Kits|Remove|TP) is at 0 players, capacity 100. Peak of 3 in the last seven days, average 0 players. Busiest window in 48 hours: 17:00 UTC, 1 players on average.

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

Alkad #3 (Max 2|Kits|Remove|TP) places #4,408 on seven-day player hours, #1,579 in Europe and in the top 20% of all ranked servers. Within the duo group it sits at #240.

Settings

Which settings and rules are confirmed on Alkad #3 (Max 2|Kits|Remove|TP)?

No gather rate appears in Alkad #3 (Max 2|Kits|Remove|TP)'s name. duo sets the cap: groups are limited to 2 players. It runs survival, gather, build, raid, as the game intends. Players can raid and fight each other here. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. It uses the word vanilla for itself: facepunch's game unaltered: rates, kits and rules unchanged. On: VAC, Valve's anti-cheat.

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

A procedural map of size 3,500 runs on Alkad #3 (Max 2|Kits|Remove|TP), generated by the game from seed 1472934234. Same size, same seed, same map. RustMaps shows it, linked from this page.

How to Join

How do you get onto Alkad #3 (Max 2|Kits|Remove|TP)?

Open the console in Rust with F1 after starting the game, then type client.connect 88.99.1.43:28035. Alternatively, Launch Rust here opens Rust via Steam and connects you. The server's website: https://m.vk.com/rust_alkad.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Standard survival mode for Rust.
mp100
Max players 100 slots on this server.
ts2
Group limit No team may exceed 2.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code The region code is unset.

Wipe schedule

^b
Biweekly Two-week wipe cycle.

Difficulty

^v
Vanilla Facepunch's game unaltered: rates, kits and rules unchanged.

Mods and access

^o
Oxide A plugin framework runs here: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it is listed under Modded.

Region

EU
Europe In the server browser it is listed 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.